From: Jeff Garzik <jeff@garzik.org>
To: Holger Macht <holger@homac.de>
Cc: Lin Ming <ming.m.lin@intel.com>,
linux-acpi@vger.kernel.org, linux-scsi@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Jeff Garzik <jgarzik@redhat.com>
Subject: Re: [PATCHv2 0/7] acpi/libata: Express dependencies for devices on dock stations and bays
Date: Thu, 09 Feb 2012 10:28:21 -0500 [thread overview]
Message-ID: <4F33E615.6070607@garzik.org> (raw)
In-Reply-To: <20120209073345.GA11121@homac.suse.de>
On 02/09/2012 02:33 AM, Holger Macht wrote:
> On Do 09. Feb - 14:46:11, Lin Ming wrote:
>> On Fri, Jan 20, 2012 at 8:18 AM, Holger Macht<holger@homac.de> wrote:
>>> Patches 2 through 5 are just a refresh of the patches from Matthew
>>> Garrett sent to this list in September 2010 [1]:
>>>
>>> Patch 1 is a new patch incorporating the corrections from James
>>> Bottomley. Patch 6, 7 and 8 make the whole patch set actually work on my
>>> test hardware (Thinkpad x60/Thinkpad T60) by fixing minor issues and
>>> compensating changes after the first submission.
>>>
>>> All patches now contain the correct Signed-off-by instead of Acked-by
>>> tags.
>>>
>>> [PATCH 1/8] scsi: Add wrapper to access and set scsi_bus_type in struct acpi_bus_type
>>> [PATCH 2/8] libata: Bind the Linux device tree to the ACPI device tree
>>> [PATCH 3/8] libata: Migrate ACPI code over to new bindings
>>> [PATCH 4/8] acpi: Add support for linking docks to the objects they contain
>>> [PATCH 5/8] libata: Add links between removable devices and docks
>>> [PATCH 6/8] libata: Generate and pass correct acpi handles
>>> [PATCH 7/8] acpi: Prevent duplicate hotplug device registration on dock stations
>>> [PATCH 8/8] libata: Use correct PCI devices
>>
>> Hi Holger,
>>
>> What's the status of these patches?
>
> They've been ACKed by both ACPI (Len Brown) and libata (James Bottomley)
> people, so I guess they are good to go and I'm waiting for someone (Jeff
> Garzik?) to pick them up.
I ACK'd for libata. It's queued in libata-dev... but looks like that
did not get pushed out. Should show up in the next linux-next.
Jeff
next prev parent reply other threads:[~2012-02-09 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 0:18 [PATCHv2 0/7] acpi/libata: Express dependencies for devices on dock stations and bays Holger Macht
2012-01-20 0:23 ` Holger Macht
2012-01-21 13:55 ` James Bottomley
2012-01-21 14:00 ` Holger Macht
2012-02-09 6:46 ` Lin Ming
2012-02-09 7:33 ` Holger Macht
2012-02-09 15:28 ` Jeff Garzik [this message]
2012-03-27 8:11 ` Lin Ming
2012-04-02 9:22 ` Holger Macht
2012-04-02 15:45 ` Jeff Garzik
2012-04-02 16:43 ` Holger Macht
2012-04-02 17:40 ` Jeff Garzik
2012-04-02 18:39 ` Holger Macht
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=4F33E615.6070607@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=holger@homac.de \
--cc=jgarzik@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mjg@redhat.com \
/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.