From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <JBottomley@parallels.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Cox <alan@linux.intel.com>, <linux-serial@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 3/5] serial: delete the MCA specific 8250 support.
Date: Thu, 17 May 2012 12:59:06 -0400 [thread overview]
Message-ID: <20120517165905.GA27789@windriver.com> (raw)
In-Reply-To: <20120517164610.GA22327@kroah.com>
[Re: [PATCH 3/5] serial: delete the MCA specific 8250 support.] On 17/05/2012 (Thu 09:46) Greg Kroah-Hartman wrote:
> On Thu, May 17, 2012 at 12:40:39PM -0400, Paul Gortmaker wrote:
> > The support for CONFIG_MCA is being removed, since the 20
> > year old hardware simply isn't capable of meeting today's
> > software demands on CPU and memory resources.
> >
> > This commit removes the MCA specific 8250 UART code.
> >
> > Cc: Alan Cox <alan@linux.intel.com>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: linux-serial@vger.kernel.org
> > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> Do you want me to take this through my tty tree, or are you sending this
> through some other means?
Since it depends on Linus pulling net-next 1st (otherwise we'll
get allyesconfig fails in tokenring), it probably makes sense for
me to just sit on all of it and then feed it to Linus after I've
seen him pull Dave's net-next with the token ring removal.
Unless someone has a better plan?
Thanks,
Paul.
--
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2012-05-17 16:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 16:40 [RFC/PATCH 0/5] Delete microchannel [CONFIG_MCA] support Paul Gortmaker
2012-05-17 16:40 ` [PATCH 1/5] arm: remove ability to select CONFIG_MCA Paul Gortmaker
2012-05-17 16:40 ` [PATCH 2/5] drivers/net: delete all code/drivers depending on CONFIG_MCA Paul Gortmaker
2012-05-17 16:51 ` Paul Gortmaker
2012-05-17 21:20 ` Paul Gortmaker
2012-05-17 22:09 ` [RFC PATCH net-next] hp100: delete VG/AnyLAN hp100 Joe Perches
2012-05-17 22:28 ` Francois Romieu
2012-05-17 22:50 ` Joe Perches
2012-05-18 19:28 ` Francois Romieu
2012-05-19 19:28 ` Joel Soete
2012-06-12 12:36 ` Pavel Machek
2012-05-17 22:23 ` [PATCH 2/5] drivers/net: delete all code/drivers depending on CONFIG_MCA David Miller
2012-05-17 16:40 ` [PATCH 3/5] serial: delete the MCA specific 8250 support Paul Gortmaker
2012-05-17 16:46 ` Greg Kroah-Hartman
2012-05-17 16:59 ` Paul Gortmaker [this message]
2012-05-17 20:16 ` David Miller
2012-05-17 21:02 ` Paul Gortmaker
2012-05-17 16:40 ` [PATCH 4/5] scsi: delete the MCA specific drivers and driver code Paul Gortmaker
2012-05-17 16:40 ` [PATCH 5/5] MCA: delete all remaining traces of microchannel bus support Paul Gortmaker
2012-05-17 18:00 ` Ingo Molnar
2012-05-17 22:18 ` H. Peter Anvin
2012-05-17 16:53 ` [RFC/PATCH 0/5] Delete microchannel [CONFIG_MCA] support Linus Torvalds
2012-05-17 17:22 ` Alan Cox
2012-05-17 17:24 ` James Bottomley
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=20120517165905.GA27789@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=JBottomley@parallels.com \
--cc=alan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=torvalds@linux-foundation.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