linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the net-next tree
Date: Thu, 16 Apr 2020 01:58:30 +0000	[thread overview]
Message-ID: <0f7e01568ecda727b75fd417865a72767258fd3b.camel@mellanox.com> (raw)
In-Reply-To: <20200413100534.057a688e@canb.auug.org.au>

On Mon, 2020-04-13 at 10:05 +1000, Stephen Rothwell wrote:
> Hi Saeed,
> 
> On Tue, 10 Mar 2020 23:57:31 +0000 Saeed Mahameed <
> saeedm@mellanox.com> wrote:
> > On Tue, 2020-03-10 at 21:01 +1100, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > Commits
> > > 
> > >   b63293e759a1 ("net/mlx5e: Show/set Rx network flow
> > > classification
> > > rules on ul rep")
> > >   6783e8b29f63 ("net/mlx5e: Init ethtool steering for
> > > representors")
> > >   01013ad355d6 ("net/mlx5e: Show/set Rx flow indir table and RSS
> > > hash
> > > key on ul rep")
> > >   
> > 
> > Hi Stephen, 
> > 
> > checkpatch doesn't seem to catch such problems.. 
> > 
> > I count on our CI to do such checks for me, so instead of me
> > writing a 
> > new script every time we hit a new unforeseen issue, i was
> > wondering
> > where can i find the set of test/scripts you are running ? 
> 
> I have attached my scripts ...
> 

Thanks Stephen ! much appreciated.

Saeed.

  reply	other threads:[~2020-04-16  1:58 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 10:01 linux-next: Signed-off-by missing for commits in the net-next tree Stephen Rothwell
2020-03-10 23:57 ` Saeed Mahameed
2020-04-13  0:05   ` Stephen Rothwell
2020-04-16  1:58     ` Saeed Mahameed [this message]
  -- 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
2019-11-25  7:28 Stephen Rothwell
2019-11-25  7:35 ` Daniel Borkmann
2019-08-15 21:53 Stephen Rothwell
2019-08-15 22:06 ` Gerd Rausch
2019-08-16  9:15   ` Andy Grover
2019-08-16 12:45     ` Chris Mason
2019-08-16 14:10     ` Gerd Rausch
2019-08-16 14:31       ` Stephen Rothwell
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=0f7e01568ecda727b75fd417865a72767258fd3b.camel@mellanox.com \
    --to=saeedm@mellanox.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
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).