From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: linux-next: manual merge of the pinctrl tree with the jc_docs tree
Date: Fri, 21 May 2021 16:01:26 +0300 [thread overview]
Message-ID: <YKevJlXRw4F3CqUf@smile.fi.intel.com> (raw)
In-Reply-To: <20210521141728.6f5e3621@canb.auug.org.au>
On Fri, May 21, 2021 at 02:17:28PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the pinctrl tree got a conflict in:
>
> include/linux/pinctrl/pinconf-generic.h
>
> between commit:
>
> 4b0c9948a4c2 ("docs: update pin-control.rst references")
>
> from the jc_docs tree and commit:
>
> 57b55eeb7552 ("pinctrl: Keep enum pin_config_param ordered by name (part 2)")
>
> 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.
Seems correct to me, thanks!
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc include/linux/pinctrl/pinconf-generic.h
> index 5a96602a3316,98ed5959ca9a..000000000000
> --- a/include/linux/pinctrl/pinconf-generic.h
> +++ b/include/linux/pinctrl/pinconf-generic.h
> @@@ -81,6 -81,10 +81,10 @@@ struct pinctrl_map
> * passed in the argument on a custom form, else just use argument 1
> * to indicate low power mode, argument 0 turns low power mode off.
> * @PIN_CONFIG_MODE_PWM: this will configure the pin for PWM
> + * @PIN_CONFIG_OUTPUT: this will configure the pin as an output and drive a
> + * value on the line. Use argument 1 to indicate high level, argument 0 to
> - * indicate low level. (Please see Documentation/driver-api/pinctl.rst,
> ++ * indicate low level. (Please see Documentation/driver-api/pin-control.rst,
> + * section "GPIO mode pitfalls" for a discussion around this parameter.)
> * @PIN_CONFIG_OUTPUT_ENABLE: this will enable the pin's output mode
> * without driving a value there. For most platforms this reduces to
> * enable the output buffers and then let the pin controller current
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-05-21 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 4:17 linux-next: manual merge of the pinctrl tree with the jc_docs tree Stephen Rothwell
2021-05-21 13:01 ` Andy Shevchenko [this message]
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=YKevJlXRw4F3CqUf@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab+huawei@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