From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Maxime Ripard <maxime.ripard@bootlin.com>
Subject: linux-next: Signed-off-by missing for commits in the arm-soc tree
Date: Wed, 3 Oct 2018 07:21:40 +1000 [thread overview]
Message-ID: <20181003072140.7c18d772@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
Hi all,
Commits
6eeb4180d4b9 ("ARM: dts: sunxi: h3-h5: Add Bananapi M2+ v1.2 device trees")
80c21c8c8b8d ("arm64: dts: allwinner: h5: Add device tree for Bananapi M2 Plus H5")
aa8fee415f46 ("ARM: dts: sun8i: h3: Split out non-SoC-specific parts of Bananapi M2 Plus")
db9fd9d13e30 ("ARM: dts: sun8i: h3: bpi-m2-plus: Fix address for external RGMII Ethernet PHY")
6c700289a3e8 ("ARM: dts: sun8i: h3-h5: ir register size should be the whole memory block")
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:[~2018-10-02 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 21:21 Stephen Rothwell [this message]
2018-10-04 19:37 ` linux-next: Signed-off-by missing for commits in the arm-soc tree Maxime Ripard
-- strict thread matches above, loose matches on Subject: below --
2022-02-27 20:45 Stephen Rothwell
2022-02-28 11:53 ` Arnd Bergmann
2021-10-27 11:53 Stephen Rothwell
2020-07-26 21:35 Stephen Rothwell
2020-07-27 7:27 ` Arnd Bergmann
2018-07-15 21:57 Stephen Rothwell
2018-07-15 22:50 ` Olof Johansson
2018-07-16 9:13 ` Florian Fainelli
2018-07-16 9:24 ` Chen-Yu Tsai
2018-07-16 9:54 ` Florian Fainelli
2018-07-16 9:57 ` Russell King - ARM Linux
2018-07-16 11:55 ` Florian Fainelli
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=20181003072140.7c18d772@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=olof@lixom.net \
/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;
as well as URLs for NNTP newsgroup(s).