summaryrefslogtreecommitdiff
path: root/util/sbase/sha384.h
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2025-12-15 14:04:21 +0000
committerLeah Rowe <leah@libreboot.org>2025-12-15 14:06:12 +0000
commitaa0e4205d657d9468b933599e091523c21bbde12 (patch)
tree34c67e9b6cc1f8b8854d08bc9afd846119191cd4 /util/sbase/sha384.h
parentf3dc54432e9df32080a062f942d8b81e2102170f (diff)
re-base the T480 thunderbolt patchHEADmaster
i noticed that the enablement patch came first, before the actual driver. while this functioned overall, it was obviously flawed in terms of the resulting git history. the person who sent the patch previously had 0046- on both patch names, which meant that alphabetical sorting caused the enablement patch to be applied before the driver patch. furthermore: it seems that the submitted had manually re-applied the same Kconfig changes in the enablement patch, adding their own name - since Kconfig is not copyrightable anyway, in this specific example, or otherwise trivial, it's probably fine, but the original author on the gerrit patch is actually Matt DeVillier: https://review.coreboot.org/c/coreboot/+/88490 I have therefore simply re-based by checking out Matt's patch, on patchset 1. However, patchset 1 of Matt's patch uses patch set 16 of: https://review.coreboot.org/c/coreboot/+/75286 HustlerOne's lbmk merge uses patchset 18: https://review.coreboot.org/c/coreboot/+/75286/18 The differences between the two can be observed, thus: https://review.coreboot.org/c/coreboot/+/75286/16..18 It should be clarified that these patches are not upstreamed yet, but under heavy review on gerrit. However, testing has revealed that the patch is mostly stable. Signed-off-by: Leah Rowe <leah@libreboot.org>
Diffstat (limited to 'util/sbase/sha384.h')
0 files changed, 0 insertions, 0 deletions