From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kamal Dasu <kdasu.kdev@gmail.com>, Rob Herring <robh@kernel.org>
Subject: Re: linux-next: manual merge of the nand tree with Linus' tree
Date: Thu, 27 Jun 2019 16:51:37 +0200 [thread overview]
Message-ID: <20190627165129.3b2c1264@xps13> (raw)
In-Reply-To: <20190604105418.58da18b2@canb.auug.org.au>
Hi Stephen,
Stephen Rothwell <sfr@canb.auug.org.au> wrote on Tue, 4 Jun 2019
10:54:18 +1000:
> Hi all,
>
> Today's linux-next merge of the nand tree got a conflict in:
>
> Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
>
> between commit:
>
> a5f2246fb913 ("dt: bindings: mtd: replace references to nand.txt with nand-controller.yaml")
>
> from Linus' tree and commit:
>
> 33cc5bd0b87a ("dt-bindings: mtd: brcmnand: Make nand-ecc-strength and nand-ecc-step-size optional")
>
> from the nand tree.
>
> I fixed it up (the latter included the changes from the former, so I
> just used that) 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.
>
Can you please share the fix? I might want to include it in the final
PR.
Thanks,
Miquèl
next prev parent reply other threads:[~2019-06-27 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 0:54 linux-next: manual merge of the nand tree with Linus' tree Stephen Rothwell
2019-06-27 14:51 ` Miquel Raynal [this message]
2019-06-27 21:22 ` Miquel Raynal
-- strict thread matches above, loose matches on Subject: below --
2019-07-01 5:23 Stephen Rothwell
2018-02-18 22:51 Stephen Rothwell
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=20190627165129.3b2c1264@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@collabora.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robh@kernel.org \
--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