From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Albert Lee <albertcc@tw.ibm.com>, IDE Linux <linux-ide@vger.kernel.org>
Subject: Re: [PATCH/RFC] Port of pdc202xx_new driver to libata
Date: Wed, 13 Oct 2004 22:16:35 +0200 [thread overview]
Message-ID: <58cb370e04101313161223717f@mail.gmail.com> (raw)
In-Reply-To: <416D88FA.1050200@pobox.com>
On Wed, 13 Oct 2004 15:58:50 -0400, Jeff Garzik <jgarzik@pobox.com> wrote:
> >>My question is, in the current kernel, the IDE subsystem drives PATA chips
> >>and libata drives SATA chips. Will PATA driver like this be accepted into
> >>libata?
> >
> >
> > My opinion is: yes but not now, final answer is of course left to Jeff.
>
> With the progress currently being made, I think my preference would be
> to start collecting PATA drivers such this in my libata-dev queue.
>
> I would not send these PATA drivers upstream until the PATA to-do items
> are complete (see other email), but it would be nice to have a central
> location (both BK and patch on kernel.org) for developers and users to
> mess with PATA support.
I was going to start libata-pata-2.6 (from libata-dev-2.6)
but this sounds even better :)
and lets ignore /dev/hda vs /dev/sda issue completely
for now in hope that udev will fix this for us etc. :)
> My own comments:
>
> >> obj-$(CONFIG_SCSI_ATA_PIIX) += libata.o ata_piix.o
> >>> +obj-$(CONFIG_SCSI_PATA_PDC_NEW) += libata.o pata_pdc202xx_new.o
> >
> >
> > why not jus pata_pdc_new? or pata_pdc_27x?
>
> I would prefer to eliminate the "_new" suffix. Other than that I don't
> really care. If I had written the driver, I would have named it
> pata_pdc202xx I suppose.
There is a high chance that somebody will also port
pdc202xx_old driver to libata so pata_pdc202xx will
be confusing.
next prev parent reply other threads:[~2004-10-13 20:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 10:06 [PATCH/RFC] Port of pdc202xx_new driver to libata Albert Lee
2004-10-13 19:32 ` Bartlomiej Zolnierkiewicz
2004-10-13 19:58 ` Jeff Garzik
2004-10-13 20:16 ` Bartlomiej Zolnierkiewicz [this message]
2004-10-18 10:30 ` Albert Lee
2004-10-18 17:00 ` Jeff Garzik
2004-10-18 17:26 ` Jeff Garzik
2004-10-21 8:36 ` Albert Lee
2004-10-21 23:10 ` Jeff Garzik
2004-10-22 2:32 ` Albert Lee
2004-10-27 14:46 ` Jeff Garzik
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=58cb370e04101313161223717f@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=albertcc@tw.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 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.