From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Philipp Stanner <pstanner@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: [PATCH v2 0/2] devres: A couple of cleanups
Date: Thu, 29 Feb 2024 17:53:38 +0200 [thread overview]
Message-ID: <20240229155507.3853059-1-andriy.shevchenko@linux.intel.com> (raw)
A couple of ad-hoc cleanups. No functional changes intended.
v2:
- fixed plural vs. singular "to have" (Philipp)
Andy Shevchenko (2):
devres: Switch to use dev_err_probe() for unification
devres: Don't use "proxy" headers
lib/devres.c | 26 +++++++++++++++-----------
1 file changed, 15 insertions(+), 11 deletions(-)
--
2.43.0.rc1.1.gbec44491f096
next reply other threads:[~2024-02-29 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 15:53 Andy Shevchenko [this message]
2024-02-29 15:53 ` [PATCH v2 1/2] devres: Switch to use dev_err_probe() for unification Andy Shevchenko
2024-02-29 20:11 ` Philipp Stanner
2024-02-29 15:53 ` [PATCH v2 2/2] devres: Don't use "proxy" headers Andy Shevchenko
2024-02-29 20:21 ` Philipp Stanner
2024-02-29 20:50 ` 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=20240229155507.3853059-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pstanner@redhat.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