public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Holger Macht <holger@homac.de>
To: Lin Ming <ming.m.lin@intel.com>
Cc: 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, 9 Feb 2012 08:33:45 +0100	[thread overview]
Message-ID: <20120209073345.GA11121@homac.suse.de> (raw)
In-Reply-To: <CAF1ivSYhOTitPctsJOTKWN9HDt0VZpQe_-_a0LnLefVGxOJtXg@mail.gmail.com>

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.

Regards,
 Holger

 
> 
> Some of my patches also need ata device binded to ACPI handle.
> I hope these patches will be merged soon.
> 
> Thanks for the great work.
> 
> Regards,
> Lin Ming
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-02-09  7:33 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 [this message]
2012-02-09 15:28     ` Jeff Garzik
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=20120209073345.GA11121@homac.suse.de \
    --to=holger@homac.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox