Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1391847 > unrolled thread

Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig option

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig  option William Breathitt Gray <vilhelm.gray@gmail.com> - 2016-05-01 18:20 +0200
    Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig  option Greg KH <gregkh@linuxfoundation.org> - 2016-05-01 23:30 +0200

#1391847 — Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig option

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@kernel.org>
>> >
>> >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.

Many thanks,

William Breathitt Gray

[toc] | [next] | [standalone]

#1391903

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@kernel.org>
> >> >
> >> >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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web