All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: akpm@linux-foundation.org
Cc: jeff@garzik.org, linux-ide@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk, alan@redhat.com, lenb@kernel.org
Subject: Re: [patch 04/30] ACPI driver support for pata
Date: Tue, 06 Mar 2007 21:54:50 +0900	[thread overview]
Message-ID: <45ED649A.20207@gmail.com> (raw)
In-Reply-To: <200703061037.l26AbrtB019463@shell0.pdx.osdl.net>

Hello,

akpm@linux-foundation.org wrote:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> 
> - Add a driver for motherboard ACPI method devices
> 
> - Link it after normal drivers so ACPI is not preferred
> 
> - Hook the AMD driver to prefer ACPI for the Nvidia devices if ACPI is
>   active
> 
> - While we are at it fix up the simplex clear the AMD driver.
> 
> Depends upon the set_mode -> do_set_mode wrapper patch
> 
> Signed-off-by: Alan Cox <alan@redhat.com>
> Cc: Jeff Garzik <jeff@garzik.org>
> Cc: Tejun Heo <htejun@gmail.com>
> Cc: Len Brown <lenb@kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---

Can't find the original posting, so replying here.  Alan, Jeff, can you
guys hold a bit with pata_acpi?  I think it's better to implement
helpers in libata-acpi and use them as necessary in sata_nv rather than
using separate pata_acpi driver (we can definitely implement pata_acpi
using the helpers).  It will reduce general confusion and allow
combining acpi cable detection with specialized device handling (e.g.
ACPI cable detection combined with ADMA command operation).

libata-acpi also needs quite some amount of other improvements.  I'll
post prototype code and things to discuss about later this week.

Thanks.

-- 
tejun

  reply	other threads:[~2007-03-06 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 10:37 [patch 04/30] ACPI driver support for pata akpm
2007-03-06 12:54 ` Tejun Heo [this message]
2007-03-06 15:14   ` Alan Cox
2007-03-06 14:18     ` Tejun Heo
2007-03-06 14:29       ` Alan Cox
2007-03-06 14:26     ` Jeff Garzik
2007-03-06 16:29       ` Alan Cox

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=45ED649A.20207@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=jeff@garzik.org \
    --cc=lenb@kernel.org \
    --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.