From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: alsa-devel@alsa-project.org, linux-scsi@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
hpa@zytor.com, tglx@linutronix.de, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig option
Date: Sun, 1 May 2016 12:17:07 -0400 [thread overview]
Message-ID: <20160501161707.GA1441@sophia> (raw)
In-Reply-To: <20160413151826.GA13959@kroah.com>
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
next prev parent reply other threads:[~2016-05-01 16:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 13:25 [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig option William Breathitt Gray
2016-04-11 13:25 ` [PATCH 1/4] pnp: pnpbios: Add explicit X86_32 dependency to PNPBIOS William Breathitt Gray
2016-04-22 23:51 ` Rafael J. Wysocki
2016-04-23 14:53 ` William Breathitt Gray
2016-05-01 15:52 ` William Breathitt Gray
2016-04-11 13:25 ` [PATCH 2/4] sound: isa: sscape: Use correct format identifier for size_t William Breathitt Gray
2016-04-11 13:54 ` Takashi Iwai
2016-04-11 13:25 ` [PATCH 3/4] scsi: ultrastor: Use correct format identifier for kernel pointer William Breathitt Gray
2016-04-11 13:25 ` [PATCH 4/4] isa: Remove the ISA_BUS Kconfig option William Breathitt Gray
2016-04-13 7:26 ` [PATCH 0/4] Decouple X86_32 dependency from the ISA " Ingo Molnar
2016-04-13 12:15 ` William Breathitt Gray
2016-04-13 14:38 ` Ingo Molnar
2016-04-13 14:48 ` William Breathitt Gray
2016-04-13 15:18 ` Greg KH
2016-05-01 16:17 ` William Breathitt Gray [this message]
2016-05-01 21:25 ` Greg KH
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=20160501161707.GA1441@sophia \
--to=vilhelm.gray@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).