From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux pin control <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [GIT PULL] intel-pinctrl for 5.9-1
Date: Tue, 21 Jul 2020 17:05:53 +0300 [thread overview]
Message-ID: <CAHp75Ve=mck42XNbLY3d5w3saOdMkbQusLjEYuNgo5HOz=9iWw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYcKKQNwk905J+mOAXY-hCx0Pku2wKikMccX6yqECT0Mw@mail.gmail.com>
On Tue, Jul 21, 2020 at 4:59 PM Linus Walleij <linus.walleij@linaro.org> wrote:
> On Tue, Jul 21, 2020 at 3:18 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>
> > ARM/orion/gpio:
> > - Make use of for_each_requested_gpio()
> >
> > at91:
> > - Make use of for_each_requested_gpio()
> (...)
> > gpio:
> > - xra1403: Make use of for_each_requested_gpio()
> > - mvebu: Make use of for_each_requested_gpio()
>
> Are these dependent on this:
>
> > gpiolib:
> > - Introduce for_each_requested_gpio_in_range() macro
>
> Because if they only need for_each_requested_gpio()
> I could just merge it to the gpio tree, since I have merged
> the immutable branch for that into both trees. Then I'd
> prefer to have one pinctrl and one gpio pull request.
>
> However if they explicitly need for_each_requested_gpio_in_range()
> I say I can compromise and merge it all into pinctrl.
It uses usual practice, i.e. merge of immutable branches. The pin
control stuff is dependent on this immutable branch (first patch).
I would like to avoid rebasing and doing it differently.
P.S. It should be no-op from Git perspective.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-07-21 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 13:18 [GIT PULL] intel-pinctrl for 5.9-1 Andy Shevchenko
2020-07-21 13:59 ` Linus Walleij
2020-07-21 14:05 ` Andy Shevchenko [this message]
2020-07-22 13:59 ` Linus Walleij
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='CAHp75Ve=mck42XNbLY3d5w3saOdMkbQusLjEYuNgo5HOz=9iWw@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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).