From: Andrew Morton <akpm@linux-foundation.org>
To: Zijun Hu <zijun_hu@icloud.com>
Cc: linux-kernel@vger.kernel.org,
"Zijun Hu" <quic_zijuhu@quicinc.com>,
",Mika Westerberg" <mika.westerberg@linux.intel.com>,
",Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH] kernel/resource: Simplify API __devm_release_region() implementation
Date: Thu, 14 Nov 2024 16:06:52 -0800 [thread overview]
Message-ID: <20241114160652.442ac4d4ee437810946aefbe@linux-foundation.org> (raw)
In-Reply-To: <e69c7536-f184-4588-bdec-62b79d39c411@icloud.com>
On Wed, 13 Nov 2024 22:07:22 +0800 Zijun Hu <zijun_hu@icloud.com> wrote:
> On 2024/10/17 23:34, Zijun Hu wrote:
> > From: Zijun Hu <quic_zijuhu@quicinc.com>
> >
> > Simplify __devm_release_region() implementation by dedicated
> > API devres_release() which have below advantages than current
> > __release_region() + devres_destroy():
> >
> > It is simpler if __devm_release_region() is undoing what
> > __devm_request_region() did, otherwise, it can avoid wrong and
> > undesired __release_region().
> >
> > Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
> > ---
> > linux-next tree has similar fixes as shown below:
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=0ee4dcafda9576910559f0471a3d6891daf9ab92
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9bd133f05b1dca5ca4399a76d04d0f6f4d454e44
> > ---
> > kernel/resource.c | 3 +--
>
> Hi Andrew,
>
> There are no maintainer or supporter for kernel/resource.c according to
> get_maintainer.pl.
>
> could you please code review for this patch?
Yup, thanks, I'll toss it onto the pile for consideration after
6.13-rc1.
prev parent reply other threads:[~2024-11-15 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 15:34 Zijun Hu
2024-11-07 1:13 ` Zijun Hu
2024-11-13 14:07 ` Zijun Hu
2024-11-15 0:06 ` Andrew Morton [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=20241114160652.442ac4d4ee437810946aefbe@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=quic_zijuhu@quicinc.com \
--cc=zijun_hu@icloud.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
all inboxes | Powered by JetHome®