Re: [PATCH v4 0/7] ZPODD patches

On Tue, 2012-07-31 at 10:40 +0800, Aaron Lu wrote: > Hi James, > > Any chance of these patches get merged into 3.6? Not 3.6 given that the series was only finalised a week into the merge window. Generally because of the merge frenzy, linux-next doesn't work very well during this period so

Re: [PATCH v4 0/7] ZPODD patches

On Tue, 2012-07-31 at 10:40 +0800, Aaron Lu wrote: Hi James, Any chance of these patches get merged into 3.6? Not 3.6 given that the series was only finalised a week into the merge window. Generally because of the merge frenzy, linux-next doesn't work very well during this period so there's

Re: [PATCH v4 0/7] ZPODD patches

Hi James, Any chance of these patches get merged into 3.6? Thanks, Aaron On 07/27/2012 05:00 PM, Aaron Lu wrote: v4: Rebase on top of Linus' tree, due to this, the problem of a missing flag in v3 is gone; Add a new function scsi_autopm_put_device_autosuspend to first mark last busy for the

Re: [PATCH v4 0/7] ZPODD patches

Hi James, Any chance of these patches get merged into 3.6? Thanks, Aaron On 07/27/2012 05:00 PM, Aaron Lu wrote: v4: Rebase on top of Linus' tree, due to this, the problem of a missing flag in v3 is gone; Add a new function scsi_autopm_put_device_autosuspend to first mark last busy for the

[PATCH v4 0/7] ZPODD patches

v4: Rebase on top of Linus' tree, due to this, the problem of a missing flag in v3 is gone; Add a new function scsi_autopm_put_device_autosuspend to first mark last busy for the device and then put autosuspend it as suggested by Oliver Neukum. Typo fix as pointed by Sergei Shtylyov. Check

[PATCH v4 0/7] ZPODD patches

v4: Rebase on top of Linus' tree, due to this, the problem of a missing flag in v3 is gone; Add a new function scsi_autopm_put_device_autosuspend to first mark last busy for the device and then put autosuspend it as suggested by Oliver Neukum. Typo fix as pointed by Sergei Shtylyov. Check