From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux pin control <linux-gpio@vger.kernel.org>
Subject: Re: [GIT PULL] intel-pinctrl for 6.13-1
Date: Fri, 1 Nov 2024 14:09:11 +0200 [thread overview]
Message-ID: <20241101120911.GX275077@black.fi.intel.com> (raw)
In-Reply-To: <CACRpkdaDBsRGntbq4wyEFxA+-ffpQN=MbAhUsoWbp2MO8SK2MA@mail.gmail.com>
Hi Linus,
On Fri, Nov 01, 2024 at 12:43:07PM +0100, Linus Walleij wrote:
> Hi Andy,
>
> On Fri, Nov 1, 2024 at 11:21 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>
> > One of the tiniest PR for Intel pin control drivers, only two changes there
> > which were in the Linux Next for some time without reported issues. Please,
> > pull for v6.13-rc1 (next cycle).
> (...)
> > The following changes since commit 42f7652d3eb527d03665b09edac47f85fb600924:
> >
> > Linux 6.12-rc4 (2024-10-20 15:19:38 -0700)
>
> Does this require stuff from rc4 or can you send it based on rc1?
>
> I know we added some ACPI ID or so for rc4 but ... that's only
> required at runtime right? Are there hard compile-time or
> textual dependencies?
It does not strictly depend on -rc4 but is that a problem pulling from
something that is based on > -rc1? I mean this is what we do all the
time in TB/USB side of things and typically apply first patches to
"next" branch on top of what was the -rcX at the moment.
Thanks!
next prev parent reply other threads:[~2024-11-01 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 10:21 [GIT PULL] intel-pinctrl for 6.13-1 Andy Shevchenko
2024-11-01 11:43 ` Linus Walleij
2024-11-01 12:09 ` Mika Westerberg [this message]
2024-11-01 22:30 ` Linus Walleij
2024-11-04 10:07 ` Mika Westerberg
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=20241101120911.GX275077@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
/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