From: "Robert P. J. Day" <rpjday@mindspring.com>
To: rae l <crquan@gmail.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/ipv4/af_inet.c: use ARRAY_SIZE macro from kernel.h instead
Date: Sun, 2 Sep 2007 02:36:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709020235420.22012@localhost.localdomain> (raw)
In-Reply-To: <91b13c310709012330n5ab23496p86423bdcd4fd08f2@mail.gmail.com>
On Sun, 2 Sep 2007, rae l wrote:
> On 9/2/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> > denis:
> >
> > if you're planning on doing this ARRAY_SIZE cleanup fairly
> > rigorously, here's an overview of what you're looking (based on a
> > fairly dumb scanning script that undoubtedly generates some false
> > positives). of course, the respective subsystem maintainers are
> > welcome to deal with them first, of course.
> >
> > p.s. and when you submit those patches, it's necessary to submit
> > them to only the appropriate subsystem mailing lists, not to the
> > LKML in general.
> I didn't realize that there's so many places to switch to
> ARRAY_SIZE, so now I wonder is this cleaning work valuable to the
> whole kernel tree? or we can keep the current state and just
> encourage new code to use ARRAY_SIZE?
that is *so* not my call. i just thought that, if you were about to
embark on this clean-up, you knew what was ahead of you. if you're
still interested in doing it, my best advice is to do it a subsystem
at a time, and submit the patches just to those subsystems or the
appropriate maintainers, rather than to the whole LKML, in order to
keep the traffic down.
and i'd encourage you to keep working on this. and if you have any
more general questions, you're better off asking on the kernel
janitors list, not LKML.
http://kerneljanitors.org/
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-09-02 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 4:59 Denis Cheng
2007-09-02 5:04 ` Robert P. J. Day
2007-09-02 6:30 ` rae l
2007-09-02 6:36 ` Robert P. J. Day [this message]
2007-09-02 10:30 ` [PATCH 1/2] net/: all net/ cleanup with ARRAY_SIZE Denis Cheng
2007-09-02 10:30 ` [PATCH 2/2] drivers/net/: all drivers/net/ " Denis Cheng
2007-09-13 4:10 ` Jeff Garzik
2007-09-16 23:42 ` [PATCH 1/2] net/: all net/ " David Miller
2007-09-20 16:49 ` rae l
2007-09-16 23:39 ` [PATCH] net/ipv4/af_inet.c: use ARRAY_SIZE macro from kernel.h instead 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=Pine.LNX.4.64.0709020235420.22012@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=crquan@gmail.com \
--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®