From: Juan Quintela <quintela@mandrakesoft.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Yoichi Yuasa <yuasa@hh.iij4u.or.jp>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: [patch] TANBAC TB0226(NEC VR4131) for v2.5
Date: Tue, 22 Apr 2003 14:15:04 +0200 [thread overview]
Message-ID: <86bryy4tkn.fsf@trasno.mitica> (raw)
In-Reply-To: <20030422140007.C15285@linux-mips.org> (Ralf Baechle's message of "Tue, 22 Apr 2003 14:00:07 +0200")
>>>>> "ralf" == Ralf Baechle <ralf@linux-mips.org> writes:
ralf> On Tue, Apr 22, 2003 at 01:40:19PM +0200, Geert Uytterhoeven wrote:
>> > I don't think there's much point in using ISO style initializers everywhere.
>> > So far the convention is only to replace the GNU-style inializer.
>> > We unfortunately have a few places where the code got inflated by at least
>> > the factor of 3 because now some code uses the ISO initializers for
>> > everything - for no good reason.
>>
>> What if someone will change struct resource in the future?
ralf> For the generic case that concern may be true - but I don't think struct
ralf> resource will change any time soon. Imagine fixing all the drivers ...
Did you noticed that "they" changed the modules? and bio?
/me think that we have already had enough _big_ breakages to learn
that not using named initializers is a bad idea.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2003-04-22 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 10:11 [patch] TANBAC TB0226(NEC VR4131) for v2.5 Yoichi Yuasa
2003-04-22 11:17 ` Juan Quintela
2003-04-22 11:36 ` Ralf Baechle
2003-04-22 11:40 ` Geert Uytterhoeven
2003-04-22 12:00 ` Ralf Baechle
2003-04-22 12:15 ` Juan Quintela [this message]
2003-04-23 1:31 ` Yoichi Yuasa
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=86bryy4tkn.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=yuasa@hh.iij4u.or.jp \
/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