From: Alan Cox <alan@linux.intel.com>
To: Barry Song <21cnbao@gmail.com>
Cc: Greg KH <greg@kroah.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-serial@vger.kernel.org, Rong Wang <Rong.Wang@csr.com>,
Bin Shi <Bin.Shi@csr.com>,
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: Wed, 19 Oct 2011 13:13:26 +0100 [thread overview]
Message-ID: <20111019131326.7722222b@bob.linux.org.uk> (raw)
In-Reply-To: <CAGsJ_4xJzL6dfSmmae8LH6kt2g1PmevgrFWgYLR3Tif8PD0bCQ@mail.gmail.com>
> i think we can go ahead through Linux W's pinmux tree. Linus, would
> you like to take care once Alan ack this.
Fine by me
WARNING: multiple messages have this Message-ID (diff)
From: alan@linux.intel.com (Alan Cox)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] UART: add CSR SiRFprimaII SoC on-chip uart drivers
Date: Wed, 19 Oct 2011 13:13:26 +0100 [thread overview]
Message-ID: <20111019131326.7722222b@bob.linux.org.uk> (raw)
In-Reply-To: <CAGsJ_4xJzL6dfSmmae8LH6kt2g1PmevgrFWgYLR3Tif8PD0bCQ@mail.gmail.com>
> i think we can go ahead through Linux W's pinmux tree. Linus, would
> you like to take care once Alan ack this.
Fine by me
next prev parent reply other threads:[~2011-10-19 12:03 UTC|newest]
Thread overview: 16+ 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-14 5:39 ` Barry Song
2011-10-18 3:39 ` Barry Song
2011-10-18 3:39 ` Barry Song
2011-10-18 18:13 ` Greg KH
2011-10-18 18:13 ` Greg KH
2011-10-19 1:19 ` Barry Song
2011-10-19 1:19 ` Barry Song
2011-10-19 12:13 ` Alan Cox [this message]
2011-10-19 12:13 ` Alan Cox
2011-10-19 22:02 ` Linus Walleij
2011-10-19 22:02 ` Linus Walleij
2011-10-20 8:37 ` Barry Song
2011-10-20 8:37 ` Barry Song
2011-10-28 2:52 ` 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=20111019131326.7722222b@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=21cnbao@gmail.com \
--cc=Baohua.Song@csr.com \
--cc=Bin.Shi@csr.com \
--cc=Rong.Wang@csr.com \
--cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.