From: Vojtech Pavlik <vojtech@suse.cz>
To: Pavel Machek <pavel@suse.cz>
Cc: Martin Dalecki <dalecki@evision-ventures.com>,
Jens Axboe <axboe@suse.de>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: IDE cleanup for 2.5.4-pre3
Date: Fri, 15 Feb 2002 22:24:32 +0100 [thread overview]
Message-ID: <20020215222432.A7631@suse.cz> (raw)
In-Reply-To: <20020208231346.GA1209@elf.ucw.cz> <20020211094230.E1957@suse.de> <20020211134443.GC20854@atrey.karlin.mff.cuni.cz> <20020211181013.K729@suse.de> <20020213225326.A10409@suse.cz> <20020214094046.B37@toy.ucw.cz> <3C6CC19C.3040608@evision-ventures.com> <20020215204510.GD5019@atrey.karlin.mff.cuni.cz>
In-Reply-To: <20020215204510.GD5019@atrey.karlin.mff.cuni.cz>; from pavel@suse.cz on Fri, Feb 15, 2002 at 09:45:10PM +0100
On Fri, Feb 15, 2002 at 09:45:10PM +0100, Pavel Machek wrote:
> My favourite cleanup would be
>
> struct ide_drive_s {} ide_drive_t;
>
> =>
>
> struct ide_drive {};
>
> and replacing all ide_drive_t with struct ide_drive...
Well, my favorite would be to kill HWIF() ...
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-02-15 21:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 23:13 IDE cleanup for 2.5.4-pre3 Pavel Machek
2002-02-11 8:42 ` Jens Axboe
2002-02-11 13:44 ` Pavel Machek
2002-02-11 17:10 ` Jens Axboe
2002-02-13 21:53 ` Vojtech Pavlik
2002-02-14 9:40 ` Pavel Machek
2002-02-15 8:06 ` Martin Dalecki
2002-02-15 12:20 ` Vojtech Pavlik
2002-02-15 12:24 ` Martin Dalecki
2002-02-15 12:37 ` Vojtech Pavlik
2002-02-15 20:45 ` Pavel Machek
2002-02-15 21:24 ` Vojtech Pavlik [this message]
2002-02-16 9:39 ` Martin Dalecki
2002-02-16 9:38 ` Martin Dalecki
2002-02-16 18:22 ` Andre Hedrick
2002-02-16 21:51 ` Martin Dalecki
[not found] ` <Pine.LNX.4.10.10202151719420.10501-100000@master.linux-ide.org>
2002-02-16 22:46 ` Pavel Machek
2002-02-17 13:52 ` Pavel Machek
2002-02-19 10:13 ` Martin Dalecki
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=20020215222432.A7631@suse.cz \
--to=vojtech@suse.cz \
--cc=axboe@suse.de \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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.