linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>, Networking <netdev@vger.kernel.org>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
	Vlad Buslov <vladbu@nvidia.com>,
	Dmytro Linkin <dlinkin@nvidia.com>,
	Simon Wunderlich <sw@simonwunderlich.de>,
	Sven Eckelmann <sven@narfation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commits in the net-next tree
Date: Sat, 21 Aug 2021 13:08:15 +1000	[thread overview]
Message-ID: <20210821130815.22b5cfc3@canb.auug.org.au> (raw)

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

Hi all,

Commits

  3202ea65f85c ("net/mlx5: E-switch, Add QoS tracepoints")
  0fe132eac38c ("net/mlx5: E-switch, Allow to add vports to rate groups")
  f47e04eb96e0 ("net/mlx5: E-switch, Allow setting share/max tx rate limits of rate groups")
  1ae258f8b343 ("net/mlx5: E-switch, Introduce rate limiting groups API")
  ad34f02fe2c9 ("net/mlx5: E-switch, Enable devlink port tx_{share|max} rate control")
  2d116e3e7e49 ("net/mlx5: E-switch, Move QoS related code to dedicated file")
  71d41c09f1fa ("batman-adv: Move IRC channel to hackint.org")

are missing a Signed-off-by from their committers.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-08-21  3:08 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-21  3:08 Stephen Rothwell [this message]
2021-08-21  6:37 ` linux-next: Signed-off-by missing for commits in the net-next tree Sven Eckelmann
  -- 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)
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
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=20210821130815.22b5cfc3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=davem@davemloft.net \
    --cc=dlinkin@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    --cc=vladbu@nvidia.com \
    /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).