From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: phasta@kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v2 0/2] devres: clean up and move percpu allocator
Date: Tue, 11 Nov 2025 19:00:50 +0200 [thread overview]
Message-ID: <aRNrwsEVu57D2Y7_@smile.fi.intel.com> (raw)
In-Reply-To: <ad28f8e0788399251c13619d05da5953dad3fa85.camel@mailbox.org>
On Tue, Nov 11, 2025 at 04:00:28PM +0100, Philipp Stanner wrote:
> On Tue, 2025-11-11 at 15:49 +0100, Andy Shevchenko wrote:
> > Clean up and move managed percpu allocator to devres.h.
> >
> > Changelog v2:
> > - fixed build error by adding a missed inclusion
>
> OK, didn't see v2. Documentation/ still missing, though.
No, you are wrong.
> But we only send new versions after waiting for >24h, don't we? :]
No need for a new version.
> > .../driver-api/driver-model/devres.rst | 1 -
Again, please read this list carefully.
> > drivers/base/devres.c | 25 -------------------
> > include/linux/device.h | 19 --------------
> > include/linux/device/devres.h | 17 +++++++++++++
> > 4 files changed, 17 insertions(+), 45 deletions(-)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-18 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 14:49 [PATCH v2 0/2] devres: clean up and move percpu allocator Andy Shevchenko
2025-11-11 14:49 ` [PATCH v2 1/2] devres: Remove unused devm_free_percpu() Andy Shevchenko
2025-11-11 14:49 ` [PATCH v2 2/2] devres: Move devm_alloc_percpu() and related to devres.h Andy Shevchenko
2025-11-11 15:00 ` [PATCH v2 0/2] devres: clean up and move percpu allocator Philipp Stanner
2025-11-11 17:00 ` Andy Shevchenko [this message]
2025-11-19 12:29 ` Danilo Krummrich
2025-11-19 13:56 ` Andy Shevchenko
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=aRNrwsEVu57D2Y7_@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phasta@kernel.org \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).