From: Christoph Hellwig <hch@infradead.org>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Cc: Manfred Spraul <manfred@colorfullife.com>,
Brian Lazara <blazara@nvidia.com>,
Christoph Hellwig <hch@infradead.org>,
Andrew de Quincey <adq@lidskialf.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] new device support for forcedeth.c second try
Date: Sat, 19 Jun 2004 17:56:06 +0100 [thread overview]
Message-ID: <20040619165606.GA7754@infradead.org> (raw)
In-Reply-To: <40D46EC4.9000007@gmx.net>
On Sat, Jun 19, 2004 at 06:50:12PM +0200, Carl-Daniel Hailfinger wrote:
> The code duplication will be addressed soon. Right now I'd like to change
> the union "u" of v1 and v2 structs to an anonymous union for better
> readability.
GCC 2.95 doesn't support anonymous unions, so we can't use it for the kernel.
next prev parent reply other threads:[~2004-06-19 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 13:21 [PATCH] new device support for forcedeth.c second try Carl-Daniel Hailfinger
2004-06-19 13:55 ` Francois Romieu
2004-06-19 14:15 ` Bartlomiej Zolnierkiewicz
2004-06-19 14:35 ` Carl-Daniel Hailfinger
2004-06-19 14:56 ` Bartlomiej Zolnierkiewicz
2004-06-19 15:08 ` Francois Romieu
2004-06-19 16:18 ` Manfred Spraul
2004-06-19 16:50 ` Carl-Daniel Hailfinger
2004-06-19 16:56 ` Christoph Hellwig [this message]
2004-06-21 3:06 ` [PATCH] new device support for forcedeth.c third try Carl-Daniel Hailfinger
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 17:10 [PATCH] new device support for forcedeth.c second try Brian Lazara
2004-06-21 17:36 ` Carl-Daniel Hailfinger
2004-06-21 19:00 ` Kalin KOZHUHAROV
2004-06-21 19:48 ` Carl-Daniel Hailfinger
2004-06-21 21:38 ` Kalin KOZHUHAROV
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=20040619165606.GA7754@infradead.org \
--to=hch@infradead.org \
--cc=adq@lidskialf.net \
--cc=blazara@nvidia.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.