linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Andy Grover <andy@groveronline.com>
Cc: Gerd Rausch <gerd.rausch@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andy Grover <andy.grover@oracle.com>,
	"Chris Mason" <chris.mason@oracle.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the net-next tree
Date: Fri, 16 Aug 2019 12:45:16 +0000	[thread overview]
Message-ID: <4265F394-B37F-43C1-85F7-15D2C030FF82@fb.com> (raw)
In-Reply-To: <e85146f3-93a0-b23f-6a6e-11e42815946d@groveronline.com>

On 16 Aug 2019, at 5:15, Andy Grover wrote:

> On 8/16/19 3:06 PM, Gerd Rausch wrote:
>> Hi,
>>
>> Just added the e-mail addresses I found using a simple "google 
>> search",
>> in order to reach out to the original authors of these commits:
>> Chris Mason and Andy Grover.
>>
>> I'm hoping they still remember their work from 7-8 years ago.
>
> Yes looks like what I was working on. What did you need from me? It's
> too late to amend the commitlogs...

Same question ;)  The missing signed-off-by is a mistake, but from the 
point of view of the DCO, these patches are totally fine by me.

-chris

  reply	other threads:[~2019-08-16 12:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 21:53 linux-next: Signed-off-by missing for commits in the net-next tree Stephen Rothwell
2019-08-15 22:06 ` Gerd Rausch
2019-08-16  9:15   ` Andy Grover
2019-08-16 12:45     ` Chris Mason [this message]
2019-08-16 14:10     ` Gerd Rausch
2019-08-16 14:31       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2022-03-06 20:22 Stephen Rothwell
2022-03-07 23:02 ` Jakub Kicinski
2022-03-07 23:19   ` Stephen Rothwell
2022-03-07 23:24     ` Jakub Kicinski
2022-01-26 20:57 Stephen Rothwell
2022-01-26 22:50 ` Russell King (Oracle)
2021-08-21  3:08 Stephen Rothwell
2021-08-21  6:37 ` Sven Eckelmann
2020-03-10 10:01 Stephen Rothwell
2020-03-10 23:57 ` Saeed Mahameed
2020-04-13  0:05   ` Stephen Rothwell
2020-04-16  1:58     ` Saeed Mahameed
2019-11-25  7:28 Stephen Rothwell
2019-11-25  7:35 ` Daniel Borkmann
2018-12-09 21:00 Stephen Rothwell
2018-12-09 21:11 ` Andrew Lunn
2018-12-09 21:33   ` Heiner Kallweit
2018-12-09 21:49     ` Andrew Lunn
2018-12-09 23:27       ` Sabrina Dubroca
2018-12-10  0:31         ` David Miller
2018-12-10  0:48           ` Stephen Rothwell
2018-12-10  0:54             ` David Miller
2018-12-10  2:05               ` Stephen Rothwell
2018-12-10  0:28     ` David Miller
2018-12-10 13:35       ` Andrew Lunn
2018-12-10 13:55         ` Sabrina Dubroca
2018-12-10  0:27   ` David Miller
2018-10-19  7:30 Stephen Rothwell
2018-04-02  2:30 Stephen Rothwell
2018-04-02  5:38 ` Johan Hedberg
2018-04-02  6:50   ` Stephen Rothwell
2018-03-02  4:52 Stephen Rothwell
2017-12-18 20:41 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=4265F394-B37F-43C1-85F7-15D2C030FF82@fb.com \
    --to=clm@fb.com \
    --cc=andy.grover@oracle.com \
    --cc=andy@groveronline.com \
    --cc=chris.mason@oracle.com \
    --cc=davem@davemloft.net \
    --cc=gerd.rausch@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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).