From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"rd.dunlab@gmail.com" <rd.dunlab@gmail.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the net-next tree
Date: Wed, 2 Oct 2019 15:12:19 -0700 [thread overview]
Message-ID: <5d671b8e-1a3e-3a32-1163-d15754ddb8b2@infradead.org> (raw)
In-Reply-To: <20191003080633.0388a91d@canb.auug.org.au>
On 10/2/19 3:06 PM, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 0f04f8ea62ce ("Minor fixes to the CAIF Transport drivers Kconfig file")
> 21d549769e79 ("Isolate CAIF transport drivers into their own menu")
> 0903102f5785 ("Clean up the net/caif/Kconfig menu")
>
> are missing a Signed-off-by from their authors.
>
> I guess <rd.dunlab@gmail.com> and <rdunlap@infradead.org> may be the
> same person? Please be consistent.
Yes. Yes, will do that.
--
~Randy
next prev parent reply other threads:[~2019-10-02 22:12 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 22:06 linux-next: Signed-off-by missing for commit in the net-next tree Stephen Rothwell
2019-10-02 22:12 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 23:15 Stephen Rothwell
2022-11-09 17:33 Stephen Rothwell
2022-01-03 21:18 Stephen Rothwell
2021-10-27 22:08 Stephen Rothwell
2021-10-25 21:41 Stephen Rothwell
2020-12-10 10:37 Stephen Rothwell
2020-12-10 10:38 ` Stephen Rothwell
2020-09-16 22:31 Stephen Rothwell
2020-09-17 5:48 ` Saeed Mahameed
2020-08-25 9:17 Stephen Rothwell
2020-08-04 22:22 Stephen Rothwell
2020-07-18 8:37 Stephen Rothwell
2020-05-28 21:00 Stephen Rothwell
2020-05-11 22:09 Stephen Rothwell
2020-04-27 22:31 Stephen Rothwell
2019-10-31 7:10 Stephen Rothwell
2019-10-31 17:40 ` David Miller
2019-10-31 18:40 ` Jeff Kirsher
2019-10-30 7:42 Stephen Rothwell
2019-09-10 14:42 Stephen Rothwell
2019-09-11 5:24 ` Luciano Coelho
2019-09-10 14:41 Stephen Rothwell
2019-09-11 9:02 ` Oleksij Rempel
2019-08-06 23:30 Stephen Rothwell
2019-08-06 23:37 ` Yifeng Sun
2019-08-07 1:54 ` Stephen Rothwell
2019-08-07 2:02 ` Yifeng Sun
2019-07-09 21:36 Stephen Rothwell
2019-01-16 21:06 Stephen Rothwell
2019-01-16 22:13 ` David Miller
[not found] ` <CALqoU4ywdKaeD_DX4pF2hOTh-LQb2N+zGhap6x4sskaf_YthJw@mail.gmail.com>
2019-01-16 23:09 ` David Miller
2018-10-01 23:34 Stephen Rothwell
2018-09-02 21:40 Stephen Rothwell
2018-09-03 5:08 ` Vakul Garg
2018-09-03 5:16 ` David Miller
2018-09-03 5:21 ` Stephen Rothwell
2018-07-28 4:21 Stephen Rothwell
2018-05-13 22:02 Stephen Rothwell
2017-11-12 20:44 Stephen Rothwell
2017-10-31 5:40 Stephen Rothwell
2017-10-31 6:14 ` Kirill Smelkov
2017-10-31 6:20 ` Eric Dumazet
2017-11-01 10:55 ` Francois Romieu
2017-11-01 12:15 ` Kirill Smelkov
2017-09-28 21:46 Stephen Rothwell
2017-08-30 16:51 Stephen Rothwell
2017-08-30 16:53 ` David Ahern
2017-08-30 17:38 ` Stephen Rothwell
2017-08-30 17:52 ` David Miller
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=5d671b8e-1a3e-3a32-1163-d15754ddb8b2@infradead.org \
--to=rdunlap@infradead.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rd.dunlab@gmail.com \
--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).