From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: David Miller <davem@davemloft.net>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
JBottomley@parallels.com, torvalds@linux-foundation.org,
alan@linux.intel.com, linux-serial@vger.kernel.org
Subject: Re: [PATCH 3/5] serial: delete the MCA specific 8250 support.
Date: Thu, 17 May 2012 17:02:20 -0400 [thread overview]
Message-ID: <20120517210219.GB27789@windriver.com> (raw)
In-Reply-To: <20120517.161656.1149344441984193661.davem@davemloft.net>
[Re: [PATCH 3/5] serial: delete the MCA specific 8250 support.] On 17/05/2012 (Thu 16:16) David Miller wrote:
> From: Paul Gortmaker <paul.gortmaker@windriver.com>
> Date: Thu, 17 May 2012 12:59:06 -0400
>
> > 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?
>
> Sounds good.
>
> Meanwhile, Paul, if you respin patch #2 I can toss that directly into
> my net-next tree since that's all networking stuff anyways.
OK. I'm just double checking with an allyesconfig on the respin of
the #2 in isolation and then I'll follow up in the #2 thread with it.
Thanks,
Paul.
>
> Thanks.
prev parent reply other threads:[~2012-05-17 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1337272841-25931-1-git-send-email-paul.gortmaker@windriver.com>
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
2012-05-17 20:16 ` David Miller
2012-05-17 21:02 ` Paul Gortmaker [this message]
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=20120517210219.GB27789@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