linux-gbmc: 5.15: Add missing Date: headers to tps53679 patches

Patches are applied with "git am" (via kgit-s2q). Anything git cannot read
out of the patch it invents at apply time: a missing "Date:" becomes the
current wall-clock time, and a missing "From:" becomes
"invalid_git config <unknown@unknown>". Either way the commit SHA -- and so
every descendant SHA, including HEAD -- changes on every build.

That makes the reconstructed kernel source tree non-reproducible. Because
obmc-phosphor-kernel-version bakes HEAD into CONFIG_LOCALVERSION,
KERNEL_VERSION/UTS_RELEASE then changes on every build, while BitBake task
hashes do not, since the SHA is a task output and is never hashed as an
input. An out-of-tree module can therefore take a legitimate sstate hit and
install into /lib/modules/<old-version>, which the running kernel cannot
find:

  modprobe: FATAL: Module dtbocfg not found in directory /lib/modules/...

Give every patch a "From:" and a timezone-qualified RFC 2822 "Date:" in its
mail header block. Dates and authors are taken from each patch body where it
records them, otherwise from the commit that introduced the file. Only
headers are added; no diff content is changed.

Tested: Builds and even with forced builds the hashes match every time
Fusion-Link: fusion2 N/A
Google-Bug-Id: 562061867
Change-Id: I374d19bf6eb28ce20be9cd88763cd4ba38984773
Signed-off-by: William A. Kennington III <wak@google.com>
2 files changed
tree: 5cd8662e74a8fdccc9787a466752b34a1aa4c01c
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-benchmark/
  5. recipes-bsp/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-google/
  11. recipes-kernel/
  12. recipes-phosphor/
  13. recipes-support/
  14. recipes-tpm1/
  15. recipes-tpm2/
  16. recipes-x86/
  17. LICENSE
  18. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.