devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabor Juhos <juhosg@openwrt.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] tty: ar933x_uart: add device tree support and binding documentation
Date: Fri, 30 Aug 2013 23:49:41 +0200	[thread overview]
Message-ID: <52211375.8040609@openwrt.org> (raw)
In-Reply-To: <20130830211327.GA30138@kroah.com>

2013.08.30. 23:13 keltezéssel, Greg Kroah-Hartman írta:
> On Thu, Aug 29, 2013 at 11:48:15AM +0200, Gabor Juhos wrote:
>> Modify the probe routine to get the port line number
>> from device tree if the 'of_node' is populated in the
>> platform device. The driver can be built as module,
>> thus add an OF specific module device table as well
>> to support module auto loading.
>>
>> This makes it possible to use the driver for AR9330
>> UART devices specified in device tree.
>>
>> Cc: devicetree@vger.kernel.org
>> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
>> ---
>> Changes since v1:
>>   - move the doc from bindings/tty/serial to bindings/serial
>>
>> The patch is agains the 'tty-next' branch of the
>> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tree
> 
> No it isn't, it fails to apply here :(

Well, it was created on top of ...

  commit 9dfe59f15195b8c5bd4c2950266877c51fc329f0
  Author: Stephen Boyd <sboyd@codeaurora.org>
  Date:   Wed Aug 28 13:32:41 2013 -0700

      ARM: dts: msm: Update uartdm compatible strings

      Let's follow the ratified DT binding and use uartdm instead of
      hsuart. This does break backwards compatibility but this
      shouldn't be a problem because the uart driver isn't probing on
      these devices without adding clock support (which isn't merged so
      far).

      Cc: David Brown <davidb@codeaurora.org>
      Acked-by: Kumar Gala <galak@codeaurora.org>
      Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
      Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

... and i can still apply the patch on top of that commit.

However the current tty-next tree contains the previous version of the patch:

  commit dd910d98a2e240443db0090b0ae8a719a4a460f8
  Author: Gabor Juhos <juhosg@openwrt.org>
  Date:   Thu Aug 29 08:44:01 2013 +0200

      tty: ar933x_uart: add device tree support and binding documentation

    Modify the probe routine to get the port line number
    from device tree if the 'of_node' is populated in the
    platform device. The driver can be built as module,
    thus add an OF specific module device table as well
    to support module auto loading.

    This makes it possible to use the driver for AR9330
    UART devices specified in device tree.

    Cc: devicetree@vger.kernel.org
    Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

And that is the reason why you can't apply v2. Probably you have missed my
preceding [1] mail.

What should I do now? Should I send a follow-up patch which moves the
documentation from 'bindings/tty/serial' to bindings/serial?

Thanks,
Gabor

http://marc.info/?l=linux-serial&m=137776943126968&w=2

--
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:[~2013-08-30 21:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  9:48 [PATCH v2] tty: ar933x_uart: add device tree support and binding documentation Gabor Juhos
2013-08-30 21:13 ` Greg Kroah-Hartman
2013-08-30 21:49   ` Gabor Juhos [this message]
2013-08-31  1:31     ` Greg Kroah-Hartman
2013-08-31  7:19       ` Gabor Juhos
2013-09-03 22:15         ` Kumar Gala
2013-09-03 22:16 ` Kumar Gala
2013-08-24 11:53   ` Gabor Juhos

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=52211375.8040609@openwrt.org \
    --to=juhosg@openwrt.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.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).