diff for duplicates of <20260317171319.GA90412@bhelgaas> diff --git a/a/1.txt b/N1/1.txt index 0fcb130..eeb6f6e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -45,3 +45,8 @@ that no end users will see any regressions or boot failures. Is there some way to verify that after this patch, none of the generated DTBs are in this half-baked situation? Some kind of automated DTB checker? + +-- +linux-phy mailing list +linux-phy@lists.infradead.org +https://lists.infradead.org/mailman/listinfo/linux-phy diff --git a/a/content_digest b/N1/content_digest index f99579c..ef28872 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -75,6 +75,11 @@ "\n" "Is there some way to verify that after this patch, none of the\n" "generated DTBs are in this half-baked situation? Some kind of\n" - automated DTB checker? + "automated DTB checker?\n" + "\n" + "-- \n" + "linux-phy mailing list\n" + "linux-phy@lists.infradead.org\n" + https://lists.infradead.org/mailman/listinfo/linux-phy -13e419e78f8aa7f2d16cb9a211e42a61ec27e8eef3ebab173daa3344c3354bc0 +59e6f648ba1be225f3bb276bde7000915e9f04e0008b05b829e4b5b844975c79
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.