From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Linux pin control" <linux-gpio@vger.kernel.org>,
linux-pwm@vger.kernel.org,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [GIT PULL] intel-pinctrl for 6.2-2
Date: Tue, 29 Nov 2022 14:16:09 +0200 [thread overview]
Message-ID: <Y4X4CQqafmtct26C@smile.fi.intel.com> (raw)
In-Reply-To: <Y4X0QUVIIddOK2+I@orome>
On Tue, Nov 29, 2022 at 01:00:01PM +0100, Thierry Reding wrote:
> On Mon, Nov 28, 2022 at 09:25:02PM +0100, Linus Walleij wrote:
> > On Tue, Nov 22, 2022 at 7:42 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> >
> > > This is an immutable tag with PWM feature enablement for Intel pin control IPs.
> > > It's targeting v6.2 and have been reviewed by all stakeholders.
> > >
> > > The idea is that PWM and pin control subsystem soak up it independently.
> >
> > I wanted to give Thierry the option to say if he's pulling this in,
> > but it needs rotation in linux-next so I've pulled it into the pin
> > control tree now.
>
> My recollection is that Andy wanted to take this through the Intel pin
> control tree, so there's no need for me to pick this up as well unless
> perhaps for conflict resolution (which I'm not seeing right now).
The idea was to have an immutable tag that all parties, who are involved,
can pull. It means if you don't need it, it's fine, since the main route
is Intel pin control as you said.
Thank you!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-29 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 18:43 [GIT PULL] intel-pinctrl for 6.2-2 Andy Shevchenko
2022-11-28 20:25 ` Linus Walleij
2022-11-29 11:53 ` Andy Shevchenko
2022-11-29 12:00 ` Thierry Reding
2022-11-29 12:16 ` 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=Y4X4CQqafmtct26C@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.