From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the mediatek tree
Date: Tue, 26 Apr 2022 08:07:06 +1000 [thread overview]
Message-ID: <20220426080706.26c6816b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
Hi all,
Commits
775ef8aaa66e ("arm64: dts: mediatek: align thermal zone node names with dtschema")
c8b8db1a173d ("arm64: dts: mediatek: align operating-points table name with dtschema")
c01d9aa630b8 ("arm64: dts: mediatek: mt8183: align Google CROS EC PWM node name with dtschema")
75a3c81bc634 ("arm64: dts: hisilicon: align 'freq-table-hz' with dtschema in UFS")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-04-25 22:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 22:07 Stephen Rothwell [this message]
2022-04-26 8:48 ` linux-next: Signed-off-by missing for commit in the mediatek tree Matthias Brugger
2022-04-26 8:52 ` Krzysztof Kozlowski
2022-04-26 8:53 ` Krzysztof Kozlowski
2022-04-26 8:55 ` Matthias Brugger
-- strict thread matches above, loose matches on Subject: below --
2025-02-24 22:17 Stephen Rothwell
2025-02-25 8:57 ` AngeloGioacchino Del Regno
2024-10-09 21:03 Stephen Rothwell
2024-10-08 20:15 Stephen Rothwell
2024-10-09 7:52 ` AngeloGioacchino Del Regno
[not found] ` <CAHc4DNKx1WLK-QnxTo-f1djCzhRq0MPqD=Z7szHw7+eZAjU1_g@mail.gmail.com>
2024-10-09 8:39 ` AngeloGioacchino Del Regno
2024-10-09 20:53 ` Konstantin Ryabitsev
2024-10-10 9:21 ` AngeloGioacchino Del Regno
2018-05-13 21:57 Stephen Rothwell
2018-05-14 10:47 ` Matthias Brugger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220426080706.26c6816b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox