From: Ludovic BARRE <ludovic.barre@st.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robherring2@gmail.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the pinctrl tree with the devicetree tree
Date: Tue, 31 Jul 2018 09:32:48 +0200 [thread overview]
Message-ID: <b9b4d0ae-e022-6d2e-5fdc-97ed49664eb7@st.com> (raw)
In-Reply-To: <20180731154243.203068c5@canb.auug.org.au>
On 07/31/2018 07:42 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the pinctrl tree got a conflict in:
>
> Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt
>
> between commit:
>
> 791d3ef2e111 ("dt-bindings: remove 'interrupt-parent' from bindings")
>
> from the devicetree tree and commit:
>
> de1d08b22974 ("dt-bindings: pinctrl: add syscfg mask parameter")
>
> from the pinctrl 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.
>
hi Stephen
thanks for the fix conflict, and the fix is OK for me.
BR
Ludo
next prev parent reply other threads:[~2018-07-31 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 5:42 linux-next: manual merge of the pinctrl tree with the devicetree tree Stephen Rothwell
2018-07-31 7:32 ` Ludovic BARRE [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-20 4:46 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=b9b4d0ae-e022-6d2e-5fdc-97ed49664eb7@st.com \
--to=ludovic.barre@st.com \
--cc=linus.walleij@linaro.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