On Sun, May 01, 2016 at 12:17:07PM -0400, William Breathitt Gray wrote: > On Wed, Apr 13, 2016 at 08:18:26AM -0700, Greg KH wrote: > >On Wed, Apr 13, 2016 at 10:48:42AM -0400, William Breathitt Gray wrote: > >> On Wed, Apr 13, 2016 at 04:38:38PM +0200, Ingo Molnar wrote: > >> >Ah, ok, so it's for enabling real hardware, not just a cleanup, right? You might > >> >want to put that info into the boilerplate mail or so. > >> > > >> >I'm perfectly fine with all the patches that touch x86 code: > >> > > >> > Acked-by: Ingo Molnar <mingo@xxxxxxxxxx> > >> > > >> >I suppose you'd like to have these in the driver tree, all in one place? > >> > > >> >Thanks, > >> > > >> > Ingo > >> > >> Ah yes, in retrospect I should have made it clear that this was for > >> supporting hardware rather than simply code cleanup. That was an > >> oversight on my part not to have made it more explicit. > >> > >> Introducing everything to the driver tree would be most convenient, thus > >> allowing me to quickly release my subsequent patches which will be > >> rebased on top of these. > > > >Ok, I can take these. > > > >thanks, > > > >greg k-h > > Forgive me for probing again; what is that status of this patchset? I'm > anxious to see them accepted to prevent the regression introduced by the > ISA_BUS configuration option from appearing in the next merge window. Not all of these patches had anything to do with the subject of this 0/4 patch, and seem to have gone in through other trees. So can you resend just the patches that are for this series that have not been picked up? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
