public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Barry Song <21cnbao@gmail.com>
Cc: alan@linux.intel.com, linux-serial@vger.kernel.org,
	Rong Wang <Rong.Wang@csr.com>, Bin Shi <Bin.Shi@csr.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	workgroup.linux@csr.com, Barry Song <Baohua.Song@csr.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] UART: add CSR SiRFprimaII SoC on-chip uart drivers
Date: Tue, 18 Oct 2011 11:13:19 -0700	[thread overview]
Message-ID: <20111018181319.GA7015@kroah.com> (raw)
In-Reply-To: <CAGsJ_4w6fGH+G9KapHXzCwMhz_NKfPdCxs7rF5hWKw2LGUpwWA@mail.gmail.com>

On Tue, Oct 18, 2011 at 11:39:11AM +0800, Barry Song wrote:
> 2011/10/14 Barry Song <Barry.Song@csr.com>:
> > From: Rong Wang <Rong.Wang@csr.com>
> >
> > SiRFprimaII is the latest generation application processor from CSR’s
> > multi-function SoC product family.
> > The SoC support codes are in arch/arm/mach-prima2 from Linux mainline
> > 3.0.
> >
> > There are three dedicated UARTs in system. This patch adds basic driver
> > support for them.
> >
> > It has used the newest pinmux subsystem from Linus Walleij.
> 
> Hi Alan, it means this patch doesn't compile until pinmux tree of
> Linus Walleij is merged into mainline.
> Now it is a linux next tree.

So should it go through the pinmux tree?  Or do you want to wait for the
3.3 kernel release to get this merged?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-10-18 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14  5:39 [PATCH v2] UART: add CSR SiRFprimaII SoC on-chip uart drivers Barry Song
2011-10-18  3:39 ` Barry Song
2011-10-18 18:13   ` Greg KH [this message]
2011-10-19  1:19     ` Barry Song
2011-10-19 12:13       ` Alan Cox
2011-10-19 22:02       ` Linus Walleij
2011-10-20  8:37         ` Barry Song
2011-10-28  2:52         ` Barry Song

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=20111018181319.GA7015@kroah.com \
    --to=greg@kroah.com \
    --cc=21cnbao@gmail.com \
    --cc=Baohua.Song@csr.com \
    --cc=Bin.Shi@csr.com \
    --cc=Rong.Wang@csr.com \
    --cc=alan@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=workgroup.linux@csr.com \
    /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