From: Joe Perches <joe@perches.com>
To: Jakub Kicinski <kuba@kernel.org>, Ronak Doshi <doshir@vmware.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Petr Vandrovec <petr@vmware.com>,
Pv-drivers <Pv-drivers@vmware.com>,
"David S. Miller" <davem@davemloft.net>,
open list <linux-kernel@vger.kernel.org>
Subject: [PATCH] checkpatch: Add kmalloc_array_node to unnecessary OOM message check
Date: Fri, 22 Jan 2021 10:37:33 -0800 [thread overview]
Message-ID: <b9dc4a808b1518e08ab8761480d9872e5d18e7cd.camel@perches.com> (raw)
In-Reply-To: <20210122095006.58d258aa@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
commit 5799b255c491 ("include/linux/slab.h: add kmalloc_array_node() and
kcalloc_node()") was added in 2017. Update the unnecessary OOM message
test to include it.
Signed-off-by: Joe Perches <joe@perches.com>
Reported-by: Jakub Kicinski <kuba@kernel.org>
---
Maybe not worth fixing, but no real effort to fix either.
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 4f8494527139..8dbf1986a8de 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -487,7 +487,7 @@ our $logFunctions = qr{(?x:
our $allocFunctions = qr{(?x:
(?:(?:devm_)?
- (?:kv|k|v)[czm]alloc(?:_node|_array)? |
+ (?:kv|k|v)[czm]alloc(?:_array)?(?:_node)? |
kstrdup(?:_const)? |
kmemdup(?:_nul)?) |
(?:\w+)?alloc_skb(?:_ip_align)? |
prev parent reply other threads:[~2021-01-22 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 2:19 [PATCH net-next] vmxnet3: Remove buf_info from device accessible structures Ronak Doshi
2021-01-22 1:07 ` Jakub Kicinski
2021-01-22 8:24 ` Ronak Doshi
2021-01-22 17:50 ` Jakub Kicinski
2021-01-22 18:37 ` Joe Perches [this message]
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=b9dc4a808b1518e08ab8761480d9872e5d18e7cd.camel@perches.com \
--to=joe@perches.com \
--cc=Pv-drivers@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petr@vmware.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).