Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>, sfr@canb.auug.org.au
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next: Signed-off-by missing for commit in the net-next tree
Date: Thu, 31 Oct 2019 11:40:15 -0700
Message-ID: <d092e42a96eb88640963a733b3b89e7c34c95c02.camel@intel.com> (raw)
In-Reply-To: <20191031.104036.906328689737801166.davem@davemloft.net>

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

On Thu, 2019-10-31 at 10:40 -0700, David Miller wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu, 31 Oct 2019 18:10:44 +1100
> 
> > Commit
> > 
> >    a7023819404a ("e1000e: Use rtnl_lock to prevent race conditions
> > between net and pci/pm")
> > 
> > is missing a Signed-off-by from its committer.
> 
> Ok Jeff, that's two pull requests I've taken from you this week where
> there were incorrect SHA1 IDs in Fixes tags or missing signoffs.
> 
> Please use some scripts or other forms of automation to keep this
> from
> happening in the future.

Not sure what is going on to remove my SOB, since everything is
scripted, but I will look into it and I will add an additional check to
ensure future pull requests are not missing anything.  I apologize for
the missing SOB's.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply index

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31  7:10 Stephen Rothwell
2019-10-31 17:40 ` David Miller
2019-10-31 18:40   ` Jeff Kirsher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-30  7:42 Stephen Rothwell
2019-10-02 22:06 Stephen Rothwell
2019-10-02 22:12 ` Randy Dunlap
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 publically 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=d092e42a96eb88640963a733b3b89e7c34c95c02.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git