From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm-soc: Xilinx zynq serial changes for v3.9
Date: Mon, 21 Jan 2013 10:30:29 -0800 [thread overview]
Message-ID: <20130121183029.GA21326@kroah.com> (raw)
In-Reply-To: <CAHTX3dJGHK7nO2tx_kUWLwhpgNsCwtnjXAJnRFUOHVx2uE589Q@mail.gmail.com>
On Mon, Jan 21, 2013 at 06:19:03PM +0100, Michal Simek wrote:
> Hi Arnd, Olof and Greg,
>
> I have two patches for xilinx uartps serial driver (the second one fix
> one issue in the first one).
> These patches has been sent to arm mailing list and also to
> device-tree mailing list.
>
> There is a change in zynq dtsi that's why I think it can go through
> arm-soc tree.
> Please let me know if this should go through Greg serial tree.
If they fix serial driver issues, I have no problem taking them through
my serial tree, just send them on as patches and I will be glad to queue
them up.
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-21 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 17:19 [GIT PULL] arm-soc: Xilinx zynq serial changes for v3.9 Michal Simek
2013-01-21 18:30 ` Greg Kroah-Hartman [this message]
2013-01-21 18:55 ` Michal Simek
2013-01-21 18:34 ` Arnd Bergmann
2013-01-21 18:53 ` Michal Simek
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=20130121183029.GA21326@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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 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.