All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: William Breathitt Gray <wbg@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Michael Walle <mwalle@kernel.org>,
	Ioana Ciornei <ioana.ciornei@nxp.com>,
	Mark Brown <broonie@kernel.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Cave-Ayland <mark.caveayland@nutanix.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 3/3] gpio: idio-16: Define fixed direction of the GPIO lines
Date: Tue, 21 Oct 2025 18:04:57 +0300	[thread overview]
Message-ID: <aPehGYRf9vCtzOA-@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=McPP6obWpnd7Y7duJDC=NLAOE7bjFN-iytDJ524nDr9mA@mail.gmail.com>

On Tue, Oct 21, 2025 at 04:49:05PM +0200, Bartosz Golaszewski wrote:
> On Tue, Oct 21, 2025 at 4:41 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Tue, Oct 21, 2025 at 09:21:38AM -0400, Bartosz Golaszewski wrote:
> > > On Mon, 20 Oct 2025 10:51:46 +0200, William Breathitt Gray
> > > <wbg@kernel.org> said:

...

> > > > Cc: stable@vger.kernel.org # ae495810cffe: gpio: regmap: add the .fixed_direction_output configuration parameter
> >
> > > Turns out, this requires commit ae495810cffe ("gpio: regmap: add the
> > > .fixed_direction_output configuration parameter") so I cannot queue it for
> > > v6.18. What do you want me to do? Send the first two ones upstream and apply
> > > this for v6.19?
> >
> > Why can't this be pulled from some IB/IT as part of the fix?
> 
> These kinds of things should be signalled before applying the patches
> that should go to an immutable branch. I would now have to rebase the
> my for-next branch.

No objections on this one, this is unfortunate.

> Also: the commit in question brings in a new feature, not a fix.

I can argue that this is part of the fix.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-10-21 15:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20  8:51 [PATCH v2 0/3] gpio: idio-16: Fix regmap initialization errors William Breathitt Gray
2025-10-20  8:51 ` [PATCH v2 1/3] gpio: 104-idio-16: Define maximum valid register address offset William Breathitt Gray
2025-10-20  8:51 ` [PATCH v2 2/3] gpio: pci-idio-16: " William Breathitt Gray
2025-10-20  8:51 ` [PATCH v2 3/3] gpio: idio-16: Define fixed direction of the GPIO lines William Breathitt Gray
2025-10-21 13:21   ` Bartosz Golaszewski
2025-10-21 14:41     ` Andy Shevchenko
2025-10-21 14:49       ` Bartosz Golaszewski
2025-10-21 15:04         ` Andy Shevchenko [this message]
2025-10-22  2:18     ` William Breathitt Gray
2025-10-22  6:50       ` Bartosz Golaszewski
2025-10-21  7:15 ` [PATCH v2 0/3] gpio: idio-16: Fix regmap initialization errors Linus Walleij
2025-10-21  9:50 ` Bartosz Golaszewski
2025-10-22  6:54 ` (subset) " Bartosz Golaszewski

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=aPehGYRf9vCtzOA-@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.caveayland@nutanix.com \
    --cc=mwalle@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wbg@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 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.