linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Linas Vepstas <linas@austin.ibm.com>,
	Jens Osterkamp <jens@de.ibm.com>,
	linuxppc-dev@ozlabs.org, Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org, paulus@samba.org,
	Andrew Morton <akpm@linux-foundation.org>,
	James K Lewis <jim@jklewis.com>
Subject: Re: [PATCHSET] libata: PATA driver for Celleb
Date: Tue, 20 Feb 2007 00:17:32 +0100	[thread overview]
Message-ID: <200702200017.32924.bzolnier@gmail.com> (raw)
In-Reply-To: <20070219234651.4a19a912@localhost.localdomain>


On Tuesday 20 February 2007 00:46, Alan wrote:
> > > into one in drivers/ide but really want splitting for libata with some
> > > kind of libata-pmac owning the shared stuff
> > 
> > You meand driver/ide/ppc/pmac.c ?
> 
> Yes
> 
> > moving them out of the macio_asic to a PCI device at one point, so yes,
> > maybe you are right, I should move the DMA bits to some "common" file
> > and split the various implementations.
> 
> I suspect it is worth doing when moving to libata at least, even if not
> for the older driver.

fully agreed, the way to go for both drivers

Bart

  reply	other threads:[~2007-02-19 23:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26  7:24 [PATCHSET] libata: PATA driver for Celleb Akira Iguchi
2007-01-26  7:46 ` Jeff Garzik
2007-02-14  5:19   ` Akira Iguchi
2007-02-14  5:19   ` Akira Iguchi
     [not found]   ` <200702140518.l1E5IoWX010896@toshiba.co.jp>
2007-02-14  5:29     ` Benjamin Herrenschmidt
2007-02-15  5:07       ` Jeff Garzik
2007-02-15  7:52         ` Benjamin Herrenschmidt
2007-02-15 10:41           ` Jens Osterkamp
2007-02-15 16:03             ` Jim Lewis
2007-02-15 17:14             ` Linas Vepstas
2007-02-15 18:09               ` Arnd Bergmann
2007-02-15 19:11                 ` Linas Vepstas
2007-02-19 21:56                 ` Alan
2007-02-19 21:21                   ` Benjamin Herrenschmidt
2007-02-19 23:46                     ` Alan
2007-02-19 23:17                       ` Bartlomiej Zolnierkiewicz [this message]
2007-02-19 23:28                         ` Benjamin Herrenschmidt
2007-02-19 23:18                       ` Benjamin Herrenschmidt
2007-02-19 21:43                   ` Benjamin Herrenschmidt
2007-02-20  8:14                   ` Geert Uytterhoeven
2007-02-15 20:46               ` Benjamin Herrenschmidt
2007-02-16  0:18                 ` [PATCHSET] spidernet, sungem_phy: consolidated patch series Linas Vepstas
2007-02-15  5:12       ` spidernet (was Re: [PATCHSET] libata: PATA driver for Celleb) Jeff Garzik
2007-02-15  7:52         ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2007-01-26  7:24 [PATCHSET] libata: PATA driver for Celleb Akira Iguchi

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=200702200017.32924.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --cc=jens@de.ibm.com \
    --cc=jim@jklewis.com \
    --cc=linas@austin.ibm.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).