From: Hauke Mehrtens <hauke@hauke-m.de>
To: backports@vger.kernel.org
Cc: johannes@sipsolutions.net, Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH 8/8] patches: patches: Restrict MTU changes to struct net_device
Date: Sun, 19 Apr 2020 19:10:39 +0200 [thread overview]
Message-ID: <20200419171039.17268-9-hauke@hauke-m.de> (raw)
In-Reply-To: <20200419171039.17268-1-hauke@hauke-m.de>
The struct ieee80211_hw got a max_mtu element, but no min_mtu element.
This spatch was also applied to this structure accidentally.
This adds the type to make sure this spatch is only applied to mtu_min
and mtu_max attributes on the net_device structure.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
---
patches/0073-netdevice-mtu-range.cocci | 6 +++---
patches/0074-netdevice-mtu-range-ifdefs.cocci | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/patches/0073-netdevice-mtu-range.cocci b/patches/0073-netdevice-mtu-range.cocci
index 7a4b6532..7afe900e 100644
--- a/patches/0073-netdevice-mtu-range.cocci
+++ b/patches/0073-netdevice-mtu-range.cocci
@@ -4,7 +4,7 @@
first_ops = 0
@both@
-expression ndevexp;
+struct net_device *ndevexp;
constant e1, e2;
identifier func;
position p;
@@ -17,7 +17,7 @@ func(...) {
}
@@
-expression ndevexp;
+struct net_device *ndevexp;
constant MAX;
identifier func;
position p != both.p;
@@ -58,7 +58,7 @@ if not(first_ops == ln):
cocci.include_match(False)
@r1 exists@
-expression ndevexp;
+struct net_device *ndevexp;
constant e1, e2;
identifier func;
@@
diff --git a/patches/0074-netdevice-mtu-range-ifdefs.cocci b/patches/0074-netdevice-mtu-range-ifdefs.cocci
index 5689f438..bb1ca95c 100644
--- a/patches/0074-netdevice-mtu-range-ifdefs.cocci
+++ b/patches/0074-netdevice-mtu-range-ifdefs.cocci
@@ -1,5 +1,5 @@
@@
-expression ndevexp;
+struct net_device *ndevexp;
expression E;
identifier func;
@@
@@ -12,7 +12,7 @@ func(...) {
}
@@
-expression ndevexp;
+struct net_device *ndevexp;
expression E;
identifier func;
@@
--
2.20.1
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2020-04-19 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 17:10 [PATCH 0/8] backports: Update to version 5.6.5 Hauke Mehrtens
2020-04-19 17:10 ` [PATCH 1/8] backports: add linux/units.h Hauke Mehrtens
2020-04-19 17:10 ` [PATCH 2/8] backports: skbuff: add skb_list_walk_safe() and skb_mark_not_on_list() Hauke Mehrtens
2020-04-19 17:10 ` [PATCH 3/8] backports: netlink: fix nla_validate_nested() Hauke Mehrtens
2020-04-19 17:10 ` [PATCH 4/8] backports: patches: Refresh on kernel 5.6.5 Hauke Mehrtens
2020-04-19 17:10 ` [PATCH 5/8] backports: patches: handle txqueue parameter in ndo_tx_timeout Hauke Mehrtens
2020-04-19 17:10 ` [PATCH 6/8] backports: rcupdate: Add rcu_replace_pointer Hauke Mehrtens
2020-04-19 17:10 ` [PATCH 7/8] backports: fs: Adapt struct proc_ops Hauke Mehrtens
2020-04-19 17:10 ` Hauke Mehrtens [this message]
2020-04-20 7:50 ` [PATCH 0/8] backports: Update to version 5.6.5 Johannes Berg
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=20200419171039.17268-9-hauke@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
/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).