From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeremy Jackson <jerj@coplanar.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux kernel IDE development process question
Date: 30 Mar 2003 16:51:21 +0100 [thread overview]
Message-ID: <1049039480.14686.7.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <1048955308.1467.20.camel@contact.skynet.coplanar.net>
On Sat, 2003-03-29 at 16:28, Jeremy Jackson wrote:
> I would like to know what code is kept in sync between 2.4/2.5
> (2.2/2.0?). This way I can start by understanding what is already being
> done. This is related to the recent "hdparm and removable IDE?" thread
> on LKML.
None of it.
> I would like to start by declaring ide_hwifs[] static, and removing the
> extern ide_hwifs from ide.h. all references to ide_hwifs[] will be
> converted to macros and/or access method functions, that return a
Feel free, its your tree. If it cleans up stuff a lot it may be a
workable change for 2.5. Don't overdo the access function stuff though
our you'll make things slower and larger.
Alan
prev parent reply other threads:[~2003-03-30 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 16:28 Jeremy Jackson
2003-03-29 17:24 ` Bartlomiej Zolnierkiewicz
2003-03-30 5:58 ` Andre Hedrick
2003-03-30 15:51 ` Alan Cox [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=1049039480.14686.7.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jerj@coplanar.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®