From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: rfc: ARRAY_AND_SIZE
Date: Fri, 09 Aug 2013 12:32:58 +0000 [thread overview]
Message-ID: <5204E17A.4090006@bfs.de> (raw)
In-Reply-To: <5204A345.5060605@bfs.de>
Am 09.08.2013 11:36, schrieb Dan Carpenter:
> On Fri, Aug 09, 2013 at 11:23:06AM +0200, Julia Lawall wrote:
>
>> Actually, it is used 226 times as function arguments, in 77 files. It is
>> used 39 times in a structure declaration.
>
> Ah... I was using cscope and so I missed ARM uses that weren't in
> my config.
>
> That's ugly, yes. But I still think the maintainers aren't going to
> appreciate patches for this since they did it deliberately.
>
This is the point why i started a RFC. There are 6 definitions
what means 5 have to go. NTL i would question the wisdom of having
that thing in the first had.
re,
wh
prev parent reply other threads:[~2013-08-09 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 8:07 rfc: ARRAY_AND_SIZE walter harms
2013-08-09 8:15 ` Julia Lawall
2013-08-09 9:10 ` Dan Carpenter
2013-08-09 9:23 ` Julia Lawall
2013-08-09 9:36 ` Dan Carpenter
2013-08-09 12:32 ` walter harms [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=5204E17A.4090006@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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