All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Networking <netdev@vger.kernel.org>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
	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 commit in the net tree
Date: Mon, 11 Dec 2023 09:09:25 +1100	[thread overview]
Message-ID: <20231211090925.7fd8f13e@canb.auug.org.au> (raw)

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

Hi all,

Commits

  762a55a54eec ("net/mlx5e: Disable IPsec offload support if not FW steering")
  4e25b661f484 ("net/mlx5e: Check the number of elements before walk TC rhashtable")
  baac8351f74c ("net/mlx5e: Reduce eswitch mode_lock protection context")
  c2bf84f1d1a1 ("net/mlx5e: Tidy up IPsec NAT-T SA discovery")
  dddb49b63d86 ("net/mlx5e: Add IPsec and ASO syndromes check in HW")
  5ad00dee43b9 ("net/mlx5e: Remove exposure of IPsec RX flow steering struct")
  94af50c0a9bb ("net/mlx5e: Unify esw and normal IPsec status table creation/destruction")
  3d42c8cc67a8 ("net/mlx5e: Ensure that IPsec sequence packet number starts from 1")
  a5e400a985df ("net/mlx5e: Honor user choice of IPsec replay window size")

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

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2023-12-10 22:35 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 22:09 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-01 15:26 linux-next: Signed-off-by missing for commit in the net tree Stephen Rothwell
2023-05-14 22:44 Stephen Rothwell
2023-03-06 21:37 Stephen Rothwell
2023-03-06 22:16 ` Heiner Kallweit
2023-03-07  0:52   ` Stephen Rothwell
2023-03-07  1:32     ` Jakub Kicinski
2023-01-11 21:07 Stephen Rothwell
2022-04-25 21:53 Stephen Rothwell
2021-11-29 20:32 Stephen Rothwell
2021-11-29 20:42 ` Jason A. Donenfeld
2021-05-19 21:46 Stephen Rothwell
2021-05-05 22:14 Stephen Rothwell
2020-09-20 19:50 Stephen Rothwell
2020-05-31 17:57 Stephen Rothwell
2019-12-07  7:18 Stephen Rothwell
2019-11-17 20:11 Stephen Rothwell
2019-11-13 20:21 Stephen Rothwell
2019-11-14  8:25 ` Marc Kleine-Budde
2019-10-15 20:36 Stephen Rothwell
2019-08-05 21:38 Stephen Rothwell
2019-08-05 21:43 ` David Miller
2019-04-13  8:30 Stephen Rothwell
2019-04-13 10:34 ` David Howells
2019-03-19  5:21 Stephen Rothwell
2019-03-18  4:50 Stephen Rothwell
2019-01-11  3:48 Stephen Rothwell
2019-01-11  6:10 ` Heiner Kallweit
2019-01-11  6:27   ` Frank Wunderlich
2019-01-11 13:58     ` Andrew Lunn
2018-11-21  5:04 Stephen Rothwell
2018-11-20  5:15 Stephen Rothwell
2018-11-20  8:25 ` Xin Long
2018-11-20 17:17   ` David Miller
2018-07-04 21:49 Stephen Rothwell
2018-05-10 21:17 Stephen Rothwell
2018-05-11  1:30 ` Hangbin Liu
2018-04-29 21:18 Stephen Rothwell
2018-02-08 22:18 Stephen Rothwell
2018-02-08  3:27 Stephen Rothwell
2017-09-19  4:43 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=20231211090925.7fd8f13e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.