All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: broonie@kernel.org
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
	Christophe Kerello <christophe.kerello@foss.st.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the nand tree with the mtd tree
Date: Mon, 21 Feb 2022 15:16:12 +0100	[thread overview]
Message-ID: <20220221151612.67a2dfbc@xps13> (raw)
In-Reply-To: <20220221135552.2196160-1-broonie@kernel.org>

Hello,

broonie@kernel.org wrote on Mon, 21 Feb 2022 13:55:52 +0000:

> Hi all,
> 
> Today's linux-next merge of the nand tree got a conflict in:
> 
>   Documentation/devicetree/bindings/mtd/nand-controller.yaml
> 
> between commit:
> 
>   751f204a6fe6f ("dt-bindings: mtd: nand-chip: Create a NAND chip description")
> 
> from the mtd tree and commit:
> 
>   cb57fae479be4 ("dt-binding: mtd: nand: Document the wp-gpios property")
> 
> from the nand 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.

Thanks for fixing it up in -next. We will anyway merge the NAND tree
into the MTD tree before sending a unique PR so Linus won't have to
handle it.

> 
> diff --cc Documentation/devicetree/bindings/mtd/nand-controller.yaml
> index 33855eb48a795,53b21aed0ac5f..0000000000000
> --- a/Documentation/devicetree/bindings/mtd/nand-controller.yaml
> +++ b/Documentation/devicetree/bindings/mtd/nand-controller.yaml
> @@@ -116,6 -154,20 +116,13 @@@ patternProperties
>             Ready/Busy pins. Active state refers to the NAND ready state and
>             should be set to GPIOD_ACTIVE_HIGH unless the signal is inverted.
>   
> +       wp-gpios:
> +         description:
> +           Contains one GPIO descriptor for the Write Protect pin.
> +           Active state refers to the NAND Write Protect state and should be
> +           set to GPIOD_ACTIVE_LOW unless the signal is inverted.
> +         maxItems: 1
> + 
>  -      secure-regions:
>  -        $ref: /schemas/types.yaml#/definitions/uint64-matrix
>  -        description:
>  -          Regions in the NAND chip which are protected using a secure element
>  -          like Trustzone. This property contains the start address and size of
>  -          the secure regions present.
>  -
>       required:
>         - reg
>   


Thanks,
Miquèl

  reply	other threads:[~2022-02-21 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 13:55 linux-next: manual merge of the nand tree with the mtd tree broonie
2022-02-21 14:16 ` Miquel Raynal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-18  0:45 Stephen Rothwell
2023-08-21  1:55 Stephen Rothwell
2023-08-21  7:27 ` Miquel Raynal

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=20220221151612.67a2dfbc@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=boris.brezillon@collabora.com \
    --cc=broonie@kernel.org \
    --cc=christophe.kerello@foss.st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.