devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-serial@vger.kernel.org, David Brown <davidb@codeaurora.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Document msm_serial bindings and support newer uartdms
Date: Wed, 28 Aug 2013 12:19:53 -0700	[thread overview]
Message-ID: <20130828191952.GC19754@codeaurora.org> (raw)
In-Reply-To: <89FFB174-E076-4309-BE9C-7DB24B31599F@codeaurora.org>

On 08/28, Kumar Gala wrote:
> 
> On Aug 27, 2013, at 7:12 PM, Stephen Boyd wrote:
> 
> > This patchset aligns the msm_serial driver more with downstream usage and
> > updates the driver's DT bindings.
> > 
> > Changes since v2:
> > * Fixed up DT review comments
> > * Dropped patches that were picked up in tty tree
> > 
> > Changes since v1:
> > * Dropped _clk postfix from {core,iface}_clk
> > * Split DT binding into two files
> > * Renamed DT binding files to match compatible strings
> > * Fixed up DT review comments
> > * Added new patch 5/5 (more than 1 char for UARTDM)
> > 
> > Stephen Boyd (2):
> >  devicetree: serial: Document msm_serial bindings
> >  ARM: dts: msm: Update uartdm compatible strings
> > 
> > .../devicetree/bindings/tty/serial/msm_serial.txt  | 27 -----------
> > .../bindings/tty/serial/qcom,msm-uart.txt          | 25 ++++++++++
> > .../bindings/tty/serial/qcom,msm-uartdm.txt        | 53 ++++++++++++++++++++++
> > arch/arm/boot/dts/msm8660-surf.dts                 |  2 +-
> > arch/arm/boot/dts/msm8960-cdp.dts                  |  2 +-
> > 5 files changed, 80 insertions(+), 29 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/tty/serial/msm_serial.txt
> > create mode 100644 Documentation/devicetree/bindings/tty/serial/qcom,msm-uart.txt
> > create mode 100644 Documentation/devicetree/bindings/tty/serial/qcom,msm-uartdm.txt
> 
> We are going with bindings/serial as one location, can you update this so the bindings are in bindings/serial/qcom...
> 

Ok I can move it. Do I have your ack on patch 2?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2013-08-28 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  0:12 [PATCH v3 0/2] Document msm_serial bindings and support newer uartdms Stephen Boyd
2013-08-28  0:12 ` [PATCH v3 1/2] devicetree: serial: Document msm_serial bindings Stephen Boyd
2013-08-28 18:13   ` Kumar Gala
2013-08-28 18:49 ` [PATCH v3 0/2] Document msm_serial bindings and support newer uartdms Kumar Gala
2013-08-28 19:19   ` Stephen Boyd [this message]
2013-08-28 19:21     ` Kumar Gala

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=20130828191952.GC19754@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=davidb@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.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).