From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Lechner <david@lechnology.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Axel Haslam <ahaslam@baylibre.com>,
Kevin Hilman <khilman@kernel.org>, Jiri Slaby <jslaby@suse.com>,
Sekhar Nori <nsekhar@ti.com>,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Alexandre Bailon <abailon@baylibre.com>,
linux-serial@vger.kernel.org,
Santosh Shilimkar <ssantosh@kernel.org>,
Franklin S Cooper Jr <fcooper@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] TI DA8xx/OMAPL13x/AM17xx/AM18xx/66AK2x UART
Date: Wed, 11 Jan 2017 09:06:30 +0100 [thread overview]
Message-ID: <20170111080630.GA28580@kroah.com> (raw)
In-Reply-To: <1483642460-6891-1-git-send-email-david@lechnology.com>
On Thu, Jan 05, 2017 at 12:54:16PM -0600, David Lechner wrote:
> This series adds a new UART port type for TI DA8xx/OMAPL13x/AM17xx/AM18xx/66AK2x
> UART. These SoCs have a non-standard register for UART power management that
> needs special handling in the UART driver.
>
> Greg, the first two patches will need to go through your tree. Sekhar and
> Santosh will pick up the 3 and 4 patches respectively.
Ok, I've now taken those two.
thanks,
greg k-h
prev parent reply other threads:[~2017-01-11 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 18:54 [PATCH v3 0/4] TI DA8xx/OMAPL13x/AM17xx/AM18xx/66AK2x UART David Lechner
2017-01-05 18:54 ` [PATCH v3 1/4] doc: DT: Add ti,da830-uart to serial/8250 bindings David Lechner
[not found] ` <1483642460-6891-1-git-send-email-david-nq/r/kbU++upp/zk7JDF2g@public.gmane.org>
2017-01-05 18:54 ` [PATCH v3 2/4] serial: 8250: Add new port type for TI DA8xx/66AK2x David Lechner
2017-01-05 18:54 ` [PATCH v3 3/4] ARM: da850: Add ti,da830-uart compatible for serial ports David Lechner
2017-01-05 18:54 ` [PATCH v3 4/4] ARM: dts: keystone: Add "ti,da830-uart" compatible string David Lechner
2017-01-11 8:06 ` Greg Kroah-Hartman [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=20170111080630.GA28580@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abailon@baylibre.com \
--cc=ahaslam@baylibre.com \
--cc=bgolaszewski@baylibre.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=jslaby@suse.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.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;
as well as URLs for NNTP newsgroup(s).