From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: linux-next: Signed-off-by missing for commit in the imx-mxs tree
Date: Mon, 24 Jun 2019 21:20:57 +0800 [thread overview]
Message-ID: <20190624132056.GC16146@dragon> (raw)
In-Reply-To: <20190624222359.62e92a15@canb.auug.org.au>
On Mon, Jun 24, 2019 at 10:23:59PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 9b5800c21b4d ("ARM: dts: imx6qdl-kontron-samx6i: add Kontron SMARC SoM Support")
>
> is missing a Signed-off-by from its author.
Thanks for spotting it, Stephen.
@Michael, would you please give your SoB? Otherwise, I will have to
back out the patch.
Shawn
next prev parent reply other threads:[~2019-06-24 13:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 12:23 linux-next: Signed-off-by missing for commit in the imx-mxs tree Stephen Rothwell
2019-06-24 13:20 ` Shawn Guo [this message]
2019-06-24 14:00 ` Michael Grzeschik
-- strict thread matches above, loose matches on Subject: below --
2025-09-11 7:25 Stephen Rothwell
2025-09-02 23:20 Stephen Rothwell
2025-06-19 11:33 Stephen Rothwell
2024-02-25 21:23 Stephen Rothwell
2023-10-10 5:49 Stephen Rothwell
2023-09-24 22:07 Stephen Rothwell
2023-07-19 22:06 Stephen Rothwell
2023-07-18 4:16 Stephen Rothwell
2023-04-10 21:27 Stephen Rothwell
2023-04-12 1:36 ` Shawn Guo
2022-04-11 5:30 Stephen Rothwell
2022-01-26 20:49 Stephen Rothwell
2021-10-05 21:05 Stephen Rothwell
2021-10-06 12:17 ` Shawn Guo
2021-07-14 22:06 Stephen Rothwell
2021-07-15 11:01 ` Shawn Guo
2020-09-06 21:34 Stephen Rothwell
2020-09-07 3:14 ` Shawn Guo
2020-05-20 10:21 Stephen Rothwell
2020-05-20 14:58 ` Shawn Guo
2020-03-16 7:43 Stephen Rothwell
2020-03-16 8:55 ` Shawn Guo
2019-10-28 20:38 Stephen Rothwell
2019-10-29 1:42 ` Shawn Guo
2018-07-11 21:41 Stephen Rothwell
2018-07-12 1:07 ` Shawn Guo
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=20190624132056.GC16146@dragon \
--to=shawnguo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=m.grzeschik@pengutronix.de \
--cc=sfr@canb.auug.org.au \
/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 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.