From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robherring2@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: linux-next: manual merge of the tty tree with the devicetree tree
Date: Mon, 8 Jun 2020 18:46:42 +0200 [thread overview]
Message-ID: <20200608164642.GA426831@kroah.com> (raw)
In-Reply-To: <20200602154824.263bf711@canb.auug.org.au>
On Tue, Jun 02, 2020 at 03:48:24PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tty tree got a conflict in:
>
> Documentation/devicetree/bindings/serial/rs485.yaml
>
> between commit:
>
> 9f60a65bc5e6 ("dt-bindings: Clean-up schema indentation formatting")
>
> from the devicetree tree and commit:
>
> 01c38ecff8b1 ("dt-bindings: serial: Add binding for rs485 bus termination GPIO")
>
> from the tty tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc Documentation/devicetree/bindings/serial/rs485.yaml
> index 8141e4aad530,a9ad17864889..000000000000
> --- a/Documentation/devicetree/bindings/serial/rs485.yaml
> +++ b/Documentation/devicetree/bindings/serial/rs485.yaml
> @@@ -39,6 -41,9 +39,10 @@@ properties
> $ref: /schemas/types.yaml#/definitions/flag
>
> rs485-rx-during-tx:
> - description: enables the receiving of data even while sending data.
> - $ref: /schemas/types.yaml#/definitions/flag
> + description: enables the receiving of data even while sending data.
> + $ref: /schemas/types.yaml#/definitions/flag
> +
> + rs485-term-gpios:
> + description: GPIO pin to enable RS485 bus termination.
> + maxItems: 1
> +...
This should now be resolved in Linus's tree.
thanks,
greg k-h
next prev parent reply other threads:[~2020-06-08 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 5:48 linux-next: manual merge of the tty tree with the devicetree tree Stephen Rothwell
2020-06-08 16:46 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-17 4:46 Stephen Rothwell
2025-04-17 5:33 ` Greg KH
2014-11-28 6:17 Stephen Rothwell
2013-08-13 5:41 Stephen Rothwell
2013-08-13 6:14 ` Greg KH
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=20200608164642.GA426831@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=robherring2@gmail.com \
--cc=sfr@canb.auug.org.au \
/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