From: Thomas Meyer <thomas@m3y3r.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/10] Use ARRAY_SIZE macro - v4.13-rc7
Date: Sun, 03 Sep 2017 14:19:31 +0200 [thread overview]
Message-ID: <1504439110050-939061377-0-diffsplit-thomas@m3y3r.de> (raw)
Use ARRAY_SIZE macro, rather than explicitly coding some variant of it
yourself.
Found with: find -type f -name "*.c" -o -name "*.h" | xargs perl -p -i -e
's/\bsizeof\s*\(\s*(\w+)\s*\)\s*\ /\s*sizeof\s*\(\s*\1\s*\[\s*0\s*\]\s*\)
/ARRAY_SIZE(\1)/g' and manual check/verification.
Run against version v4.13-rc7
Let me know when you as a maintainer are not interested in these kind of patches.
I can exclude you by path; e.g. all findings in "drivers/scsi" will never
be reported again by this semi-automatic program runs.
next reply other threads:[~2017-09-03 12:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 12:19 Thomas Meyer [this message]
2017-09-03 12:19 ` [PATCH 6/10] ixgbe: Use ARRAY_SIZE macro Thomas Meyer
2017-09-05 18:50 ` David Miller
2017-09-05 19:45 ` Thomas Meyer
2017-09-05 20:01 ` Joe Perches
2017-09-05 21:22 ` David Miller
2017-09-06 9:08 ` Thomas Meyer
2017-09-06 15:19 ` Joe Perches
2017-09-03 12:19 ` [PATCH 1/10] KVM: PPC: Book3S HV: " Thomas Meyer
2017-10-19 3:44 ` Paul Mackerras
2017-09-03 12:19 ` [PATCH 9/10] [SCSI] bfa: " Thomas Meyer
2017-09-03 12:19 ` [PATCH 2/10] drm/amdgpu: " Thomas Meyer
2017-09-03 12:19 ` [PATCH 4/10] drm/nouveau/bios/init: " Thomas Meyer
2017-09-03 12:19 ` [PATCH 8/10] ath9k: " Thomas Meyer
2017-09-25 7:15 ` [8/10] " Kalle Valo
2017-09-03 12:19 ` [PATCH 7/10] net/mlx4_core: " Thomas Meyer
2017-09-03 13:14 ` Tariq Toukan
2017-09-05 18:50 ` David Miller
2017-09-03 12:19 ` [PATCH 3/10] drm/i915/gvt: " Thomas Meyer
2017-09-03 12:19 ` [PATCH 5/10] [media] lgdt3306a: " Thomas Meyer
2017-09-03 12:19 ` [PATCH 10/10] staging/atomisp: " Thomas Meyer
2017-09-03 15:36 ` [PATCH 0/10] Use ARRAY_SIZE macro - v4.13-rc7 Joe Perches
2017-09-03 19:59 ` Thomas Meyer
2017-09-03 20:20 ` Joe Perches
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=1504439110050-939061377-0-diffsplit-thomas@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®