From: Tejun Heo <tj@kernel.org>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Dirk Griesbach <spamthis@freenet.de>,
Dimitris Damigos <damigos@freemail.gr>,
Dan van der Ster <dan@vanderster.com>, Jeff Wu <jeff.wu@amd.com>,
Aaron Lu <aaron.lwe@gmail.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
James Bottomley <James.Bottomley@HansenPartnership.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: Thu, 22 Aug 2013 14:36:18 -0400 [thread overview]
Message-ID: <20130822183618.GB3490@mtj.dyndns.org> (raw)
In-Reply-To: <5215BA84.20000@intel.com>
Hello, Aaron.
On Thu, Aug 22, 2013 at 03:15:16PM +0800, Aaron Lu wrote:
> The patch series has two patches and the first has been taken, shall I
> send the 2nd one again without the RFC tag in the patch subject? There
> should be no other changes at the moment.
Yes, that was a request for you to send an updated patch. I'm okay
with taking some risk with ACPI support for PMPs. It most likely
won't matter as long as the code itself doesn't oops anyway, but can
you please describe what's tested and what's not but should be okay in
the patch description?
Thanks.
--
tejun
next prev parent reply other threads:[~2013-08-22 18:36 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
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 [this message]
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=20130822183618.GB3490@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aaron.lu@intel.com \
--cc=aaron.lwe@gmail.com \
--cc=damigos@freemail.gr \
--cc=dan@vanderster.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=spamthis@freenet.de \
/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).