linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the arm-soc tree
Date: Wed, 9 Dec 2020 23:02:35 +0100	[thread overview]
Message-ID: <CAK8P3a0ivVR8oMTjLPbhWbSbtd=q3kB=zhDCmowjVWTe-k1oCQ@mail.gmail.com> (raw)
In-Reply-To: <20201210083553.73aaf0b4@canb.auug.org.au>

On Wed, Dec 9, 2020 at 10:35 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
>   2305d20f251d ("firmware: xilinx: Mark pm_api_features_map with static keyword")
>
> is missing a Signed-off-by from its committer.

Thanks for pointing it out. Just when I apply two last fixes before
sending out the
fixes pull request to Linus, I make a mess of the trivial fix...

       Arnd

  reply	other threads:[~2020-12-09 22:03 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 21:35 linux-next: Signed-off-by missing for commit in the arm-soc tree Stephen Rothwell
2020-12-09 22:02 ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-16 21:53 Stephen Rothwell
2023-10-17  9:29 ` Arnd Bergmann
2023-10-19 11:26   ` Matthias Brugger
2023-03-19 21:23 Stephen Rothwell
2023-03-19 21:27 ` Arnd Bergmann
2023-02-13 20:55 Stephen Rothwell
2023-02-13 20:57 ` Stephen Rothwell
2023-02-13 21:14   ` Arnd Bergmann
2022-03-08 21:19 Stephen Rothwell
2022-03-02 11:19 Stephen Rothwell
2022-03-01 20:56 Stephen Rothwell
2022-03-01 20:57 ` Stephen Rothwell
2022-03-01 21:14   ` Arnd Bergmann
2021-10-20 21:14 Stephen Rothwell
2021-10-14 22:29 Stephen Rothwell
2021-10-14 23:21 ` Florian Fainelli
2021-10-15  8:21   ` nicolas saenz julienne
2021-04-05 22:11 Stephen Rothwell
2021-04-05 22:11 ` Stephen Rothwell
2021-04-06 21:44   ` Arnd Bergmann
2021-04-07 11:46     ` Maxime Ripard
2021-02-09 21:18 Stephen Rothwell
2021-02-02 19:57 Stephen Rothwell
2021-02-02 20:04 ` Stephen Rothwell
2021-02-02 20:54   ` Arnd Bergmann
2020-12-09 11:01 Stephen Rothwell
2020-05-21 22:24 Stephen Rothwell
2020-05-22  1:27 ` Masahiro Yamada
2020-05-22  8:09   ` Arnd Bergmann
2020-04-19 22:11 Stephen Rothwell
2020-04-19 22:13 ` Stephen Rothwell
2020-04-20 15:18   ` Tony Lindgren
2020-04-20 19:44     ` Arnd Bergmann
2020-01-12 19:58 Stephen Rothwell
2020-01-12 19:59 ` Olof Johansson
2020-01-13  0:38   ` Stephen Rothwell
2020-01-13  8:17     ` Alexandre Torgue
2020-01-13 11:46       ` Stephen Rothwell
2020-01-13 17:52         ` Olof Johansson
2020-01-16 19:58     ` Florian Fainelli
2020-01-17 18:45     ` Olof Johansson
2020-01-09  8:56 Stephen Rothwell
2019-06-25 22:12 Stephen Rothwell
2019-06-25 22:15 ` Florian Fainelli
2018-11-03  3:57 Stephen Rothwell
2018-11-03  5:31 ` Olof Johansson
2018-05-14 21:22 Stephen Rothwell
2018-05-15  7:15 ` Alexandre Torgue
2018-05-26  4:34   ` Stephen Rothwell
2018-03-15 20:56 Stephen Rothwell
2018-03-15 21:06 ` Arnd Bergmann
2018-03-15 21:38   ` Stephen Rothwell
2018-03-16  7:34   ` Patrice CHOTARD
2018-03-22 21:01     ` Alexandre Belloni
2018-03-23  7:38       ` Patrice CHOTARD
2018-01-23  5:16 Stephen Rothwell
2018-01-23  9:16 ` Arnd Bergmann
2017-12-03 21:32 Stephen Rothwell
2017-12-04  3:41 ` Olof Johansson
2017-12-04 18:02   ` Kevin Hilman
2017-08-30 13:07 Stephen Rothwell
2017-08-30 13:19 ` Alexandre Belloni
2017-08-30 16:21   ` Olof Johansson
2017-08-30 16:42     ` Alexandre Belloni
2017-08-30 17:21     ` Stephen Rothwell

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='CAK8P3a0ivVR8oMTjLPbhWbSbtd=q3kB=zhDCmowjVWTe-k1oCQ@mail.gmail.com' \
    --to=arnd@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --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 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).