linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Tejun Heo <tj@kernel.org>
Cc: Aaron Lu <aaron.lu@intel.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Jeff Wu <jeff.wu@amd.com>, Shane Huang <shane.huang@amd.com>,
	Matthew Garrett <mjg@redhat.com>, Holger Macht <holger@homac.de>,
	Zhang Rui <rui.zhang@intel.com>,
	linux-ide@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] ata: acpi: rework the ata acpi bind support
Date: Sat, 27 Jul 2013 07:34:21 +0100	[thread overview]
Message-ID: <20130727063421.GA7393@srcf.ucam.org> (raw)
In-Reply-To: <20130725145229.GB26107@mtj.dyndns.org>

On Thu, Jul 25, 2013 at 10:52:29AM -0400, Tejun Heo wrote:
> 
> I like it but am wondering why we weren't doing this before.  Was the
> acpi support added before we made ata objects proper devices?

Yes.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2013-07-27  6:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  5:47 [RFC PATCH 0/2] Rework ATA ACPI binding code Aaron Lu
2013-07-25  5:47 ` [RFC PATCH 1/2] ata: acpi: remove dead code for ata_acpi_(un)bind Aaron Lu
2013-07-25 14:50   ` Tejun Heo
2013-07-25  5:47 ` [RFC PATCH 2/2] ata: acpi: rework the ata acpi bind support Aaron Lu
2013-07-25 14:52   ` Tejun Heo
2013-07-26  1:37     ` Aaron Lu
2013-07-26 12:48       ` Rafael J. Wysocki
2013-07-27  6:34     ` Matthew Garrett [this message]
2013-08-15  1:33     ` Aaron Lu
2013-08-15  3:19       ` Tejun Heo
2013-08-22  7:15         ` Aaron Lu
2013-08-22 18:36           ` Tejun Heo
2013-08-23  2:17             ` [PATCH " Aaron Lu
2013-08-23 16:11               ` Tejun Heo
2013-08-23  7:02           ` [RFC PATCH " Dirk Griesbach
2013-08-23  7:08             ` Aaron Lu

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=20130727063421.GA7393@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=aaron.lu@intel.com \
    --cc=holger@homac.de \
    --cc=jeff.wu@amd.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.com \
    --cc=shane.huang@amd.com \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).