From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Wentao Guan <guanwentao@uniontech.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: andy@kernel.org, mathieu.dubois-briand@bootlin.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
zhanjun@uniontech.com, niecheng1@uniontech.com,
stable@vger.kernel.org, WangYuli <wangyl5933@chinaunicom.cn>
Subject: Re: [PATCH] gpio: regmap: Fix gpio_remap_register
Date: Wed, 3 Dec 2025 12:04:21 +0200 [thread overview]
Message-ID: <aTALJckmUxkyeMBG@smile.fi.intel.com> (raw)
In-Reply-To: <20251203020342.2564767-1-guanwentao@uniontech.com>
+Cc: Ioana
On Wed, Dec 03, 2025 at 10:03:42AM +0800, Wentao Guan wrote:
> Because gpiochip_add_data successfully done, use
gpiochip_add_data()
> err_remove_gpiochip instead of err_free_bitmap to free
> such as gdev,descs..
What does 'gdev,desc.' stand for (also notice dot at the end)?
> Fixes: 553b75d4bfe9 ("gpio: regmap: Allow to allocate regmap-irq device")
Perhaps you also want to add this
ae495810cffe ("gpio: regmap: add the .fixed_direction_output configuration parameter")
As the patch changed the logic from the original commit.
Interestingly the 3bd44edd6c55 ("gpio: regmap: fix memory leak of gpio_regmap
structure") fixed one leak and missed this one.
...
> struct gpio_regmap *gpio_regmap_register(const struct gpio_regmap_config *config
> config->regmap_irq_line, config->regmap_irq_flags,
> 0, config->regmap_irq_chip, &gpio->irq_chip_data);
> if (ret)
> - goto err_free_bitmap;
> + goto err_remove_gpiochip;
>
> irq_domain = regmap_irq_get_domain(gpio->irq_chip_data);
> } else
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-12-03 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 2:03 [PATCH] gpio: regmap: Fix gpio_remap_register Wentao Guan
2025-12-03 10:04 ` Andy Shevchenko [this message]
2025-12-03 13:51 ` Wentao Guan
2025-12-03 13:46 ` 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=aTALJckmUxkyeMBG@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=andy@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