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>,
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-next tree
Date: Tue, 4 Jan 2022 08:18:42 +1100 [thread overview]
Message-ID: <20220104081842.0fd7d1e2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
Hi all,
Commits
aa36c94853b2 ("net/mlx5: Set SMFS as a default steering mode if device supports it")
4ff725e1d4ad ("net/mlx5: DR, Ignore modify TTL if device doesn't support it")
cc2295cd54e4 ("net/mlx5: DR, Improve steering for empty or RX/TX-only matchers")
f59464e257bd ("net/mlx5: DR, Add support for matching on geneve_tlv_option_0_exist field")
09753babaf46 ("net/mlx5: DR, Support matching on tunnel headers 0 and 1")
8c2b4fee9c4b ("net/mlx5: DR, Add misc5 to match_param structs")
0f2a6c3b9219 ("net/mlx5: Add misc5 flow table match parameters")
b54128275ef8 ("net/mlx5: DR, Warn on failure to destroy objects due to refcount")
e3a0f40b2f90 ("net/mlx5: DR, Add support for UPLINK destination type")
9222f0b27da2 ("net/mlx5: DR, Add support for dumping steering info")
7766c9b922fe ("net/mlx5: DR, Add missing reserved fields to dr_match_param")
89cdba3224f0 ("net/mlx5: DR, Add check for flex parser ID value")
08fac109f7bb ("net/mlx5: DR, Rename list field in matcher struct to list_node")
32e9bd585307 ("net/mlx5: DR, Remove unused struct member in matcher")
c3fb0e280b4c ("net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_"")
84dfac39c61f ("net/mlx5: DR, Fix error flow in creating matcher")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-01-03 21:18 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 21:18 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 23:15 linux-next: Signed-off-by missing for commit in the net-next tree Stephen Rothwell
2022-11-09 17:33 Stephen Rothwell
2021-10-27 22:08 Stephen Rothwell
2021-10-25 21:41 Stephen Rothwell
2020-12-10 10:37 Stephen Rothwell
2020-12-10 10:38 ` Stephen Rothwell
2020-09-16 22:31 Stephen Rothwell
2020-09-17 5:48 ` Saeed Mahameed
2020-08-25 9:17 Stephen Rothwell
2020-08-04 22:22 Stephen Rothwell
2020-07-18 8:37 Stephen Rothwell
2020-05-28 21:00 Stephen Rothwell
2020-05-11 22:09 Stephen Rothwell
2020-04-27 22:31 Stephen Rothwell
2019-10-31 7:10 Stephen Rothwell
2019-10-31 17:40 ` David Miller
2019-10-31 18:40 ` Jeff Kirsher
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 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=20220104081842.0fd7d1e2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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).