From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752473AbcEAVZf (ORCPT ); Sun, 1 May 2016 17:25:35 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:59052 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752173AbcEAVZd (ORCPT ); Sun, 1 May 2016 17:25:33 -0400 Date: Sun, 1 May 2016 14:25:32 -0700 From: Greg KH To: William Breathitt Gray Cc: Ingo Molnar , tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig option Message-ID: <20160501212532.GA8337@kroah.com> References: <20160413072602.GA7629@gmail.com> <20160413121515.GA23870@sophia> <20160413143838.GD5867@gmail.com> <20160413144842.GA26005@sophia> <20160413151826.GA13959@kroah.com> <20160501161707.GA1441@sophia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160501161707.GA1441@sophia> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > >> > > >> >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