linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the imx-mxs tree
Date: Wed, 20 May 2020 20:21:15 +1000	[thread overview]
Message-ID: <20200520202115.5409186e@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 186 bytes --]

Hi all,

Commit

  089795766399 ("arm64: dts: ls1028a: sl28: keep switch port names consistent")

is missing a Signed-off-by from its committer.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-05-20 10:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 10:21 Stephen Rothwell [this message]
2020-05-20 14:58 ` linux-next: Signed-off-by missing for commit in the imx-mxs tree Shawn Guo
  -- strict thread matches above, loose matches on Subject: below --
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-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
2019-06-24 12:23 Stephen Rothwell
2019-06-24 13:20 ` Shawn Guo
2019-06-24 14:00   ` Michael Grzeschik
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=20200520202115.5409186e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=shawnguo@kernel.org \
    /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).