On Fri, Jun 01, 2012 at 07:23:00PM +0000, KY Srinivasan wrote: > > > > -----Original Message----- > > From: Greg KH [mailto:[email protected]] > > Sent: Friday, June 01, 2012 12:26 PM > > To: Victor Miasnikov > > Cc: [email protected]; Jonathan Nieder; [email protected]; > > KY > > Srinivasan > > Subject: Re: Linux on Hyper-V 1) cd006086fa5d ata_piix: defer disks to the > > Hyper- > > V drivers by default 2) db63a4c8115a libata: add a host flag to ignore > > detected > > ATA device FW: use hv_storvsc instead of ata_piix to handle the IDE disks > > devices > > ( but not for the ... > > > > On Fri, Jun 01, 2012 at 07:17:33PM +0300, Victor Miasnikov wrote: > > > Hi! > > > > > > >> cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default > > > >>and its prerequisite > > > >> db63a4c8115a libata: add a host flag to ignore detected ATA devices > > > > > > >Sorry, but I don't see how this meets the rules for the stable trees, do > > > >you? If > > so, please show me how. > > > > > > About "how" -- ask K.Y. Srinivasan > > > > > > Hyper-V admins need _worked_ Linux v3.4.X / v3.3.X / v3.2.X > > > > > > Please, _fix_ errors related "use hv_storvsc instead of ata_piix to > > > handle the IDE disks devices ( but not for the CD-ROM)" > > > > Ok, I'll wait for KY to explain this. > > Greg, > > Clearly I cannot tell you anything about this that you don't know! Looking at > the > rules for stable tree patches, this patch does not satisfy the requirement > that > the patch fix a bug since we are changing the behavior here of the ata driver > to > accommodate Hyper-V. I don't know how much flexibility you have here for > taking patches that improve the general usability of Linux in different > environments. All I can say is that It will be nice to have this patch in > previous stable > releases.
Lots of things would be "nice", but as this doesn't meet the stable_kernel_rules.txt rules, sorry, I can't take them. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
