From: Jes Sorensen <jes@sgi.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Jiri Slaby <jirislaby@gmail.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] CodingStyle: add typedefs chapter
Date: 02 May 2006 09:17:34 -0400 [thread overview]
Message-ID: <yq0d5ewr2fl.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <1146517650.1921.55.camel@shinybook.infradead.org>
>>>>> "David" == David Woodhouse <dwmw2@infradead.org> writes:
David> On Mon, 2006-05-01 at 23:01 +0200, Jan Engelhardt wrote:
>> find rc3 -type f -print0 | xargs -0 perl -i -pe
>> 's/\btask_t\b/struct task_struct'
>>
>> + a compile test afterwards. Something I missed? (Besides that
>> lines may get longer and violate the 80-column CodingStyle rule.)
David> If we're going to do that, we might as well make it 'struct
David> task'. The additional '_struct' is redundant.
There were some long discussions about that a couple of years ago. I
believe Linus stated that he preferred _struct for those things.
It is also less likely to hit name clashes.
Jes
next prev parent reply other threads:[~2006-05-02 13:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 0:44 Randy.Dunlap
2006-05-01 7:28 ` Michael Buesch
2006-05-01 15:34 ` Randy.Dunlap
2006-05-01 14:00 ` Jan Engelhardt
2006-05-01 14:19 ` Alexey Dobriyan
2006-05-01 14:46 ` linux-os (Dick Johnson)
2006-05-01 15:01 ` Jiri Slaby
2006-05-01 15:33 ` Artem B. Bityutskiy
2006-05-01 16:58 ` David Woodhouse
2006-05-01 20:20 ` Jan Engelhardt
2006-05-01 20:45 ` Jiri Slaby
2006-05-01 21:01 ` Jan Engelhardt
2006-05-01 21:07 ` David Woodhouse
2006-05-01 21:38 ` Alexey Dobriyan
2006-05-02 10:40 ` Jörn Engel
2006-05-02 13:17 ` Jes Sorensen [this message]
2006-05-01 17:06 ` David Woodhouse
2006-05-01 20:48 ` Randy.Dunlap
2006-05-02 0:37 ` Johannes Stezenbach
2006-05-02 13:28 ` David Woodhouse
2006-05-02 14:20 ` Johannes Stezenbach
2006-05-02 14:31 ` David Woodhouse
2006-05-02 17:11 ` Randy.Dunlap
2006-05-02 18:41 ` Linus Torvalds
2006-05-02 18:50 ` David Woodhouse
2006-05-02 19:07 ` Linus Torvalds
2006-05-02 19:20 ` Marcel Siegert
2006-05-02 19:44 ` Linus Torvalds
2006-05-02 23:22 ` David Woodhouse
2006-05-03 19:41 ` Randy.Dunlap
2006-05-03 21:52 ` David Woodhouse
2006-05-03 22:09 ` Randy.Dunlap
2006-05-03 22:10 ` David Woodhouse
2006-05-01 21:23 ` Daniel Barkalow
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=yq0d5ewr2fl.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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
Powered by JetHome