From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robherring2@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
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 staging tree with the devicetree tree
Date: Tue, 6 Oct 2020 10:18:22 +0200 [thread overview]
Message-ID: <20201006081822.GA11962@kroah.com> (raw)
In-Reply-To: <20201006184944.22985fd1@canb.auug.org.au>
On Tue, Oct 06, 2020 at 06:49:44PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml
>
> between commit:
>
> 41fb845621ea ("dt-bindings: Another round of adding missing 'additionalProperties'")
>
> from the devicetree tree and commit:
>
> 3b17dd220432 ("dt-bindings: iio: adc: exynos-adc: require second interrupt with touch screen")
>
> from the staging 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/iio/adc/samsung,exynos-adc.yaml
> index 16d76482b4ff,37d6591ff78c..000000000000
> --- a/Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml
> @@@ -107,8 -109,15 +109,17 @@@ allOf
> items:
> - const: adc
>
> + - if:
> + required:
> + - has-touchscreen
> + then:
> + properties:
> + interrupts:
> + minItems: 2
> + maxItems: 2
> +
> +additionalProperties: false
> +
> examples:
> - |
> adc: adc@12d10000 {
Looks good to me, thanks!
greg k-h
next prev parent reply other threads:[~2020-10-06 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 7:49 linux-next: manual merge of the staging tree with the devicetree tree Stephen Rothwell
2020-10-06 8:18 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-27 7:53 Stephen Rothwell
2018-07-27 8:36 ` Greg KH
2017-01-20 2:55 Stephen Rothwell
2017-01-20 3:17 ` Rob Herring
2017-01-20 8:30 ` Greg KH
2017-01-20 17:24 ` Jonathan Cameron
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=20201006081822.GA11962@kroah.com \
--to=greg@kroah.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).