linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wentao Guan <guanwentao@uniontech.com>
Cc: brgl <brgl@kernel.org>,
	"mathieu.dubois-briand" <mathieu.dubois-briand@bootlin.com>,
	"Ioana Ciornei" <ioana.ciornei@nxp.com>,
	linux-gpio <linux-gpio@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	占俊 <zhanjun@uniontech.com>, 聂诚 <niecheng1@uniontech.com>,
	stable <stable@vger.kernel.org>,
	WangYuli <wangyl5933@chinaunicom.cn>
Subject: Re: [PATCH v2] gpio: regmap: Fix memleak in gpio_remap_register
Date: Wed, 3 Dec 2025 18:58:06 +0200	[thread overview]
Message-ID: <aTBsHvvpw-avP93a@smile.fi.intel.com> (raw)
In-Reply-To: <tencent_7AA5492F0C3086555B6EF720@qq.com>

On Wed, Dec 03, 2025 at 11:12:39PM +0800, Wentao Guan wrote:
> Hello Andy:
> 
> I did not found ae495810cffe ,thought it is that:
> Fixes: 00aaae60faf5 ("gpio: regmap: add the .fixed_direction_output configuration parameter"),


> I will add it to v3.

No, please don't. This is wrong.

$ git tag --contains ae495810cffe
next-20251022
...

$ git branch -a --contains ae495810cffe | grep gpio
  remotes/brgl/gpio/for-current
  remotes/brgl/gpio/for-next

So it will be part of v6.19-rc1, which means your patch should be based
on that three.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2025-12-03 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 14:15 [PATCH v2] gpio: regmap: Fix memleak in gpio_remap_register Wentao Guan
2025-12-03 14:50 ` Andy Shevchenko
2025-12-03 15:12   ` Wentao Guan
2025-12-03 16:58     ` 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=aTBsHvvpw-avP93a@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=brgl@kernel.org \
    --cc=guanwentao@uniontech.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=niecheng1@uniontech.com \
    --cc=stable@vger.kernel.org \
    --cc=wangyl5933@chinaunicom.cn \
    --cc=zhanjun@uniontech.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).