From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: "Fabio M. De Francesco" <fabio.maria.de.francesco@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Dan Williams <dan.j.williams@intel.com>,
<linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
<linux-cxl@vger.kernel.org>, Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH 0/2] Add cond_guard() to conditional guards
Date: Mon, 5 Feb 2024 10:56:06 +0000 [thread overview]
Message-ID: <20240205105606.00000546@Huawei.com> (raw)
In-Reply-To: <20240204173105.935612-1-fabio.maria.de.francesco@linux.intel.com>
On Sun, 4 Feb 2024 18:31:03 +0100
"Fabio M. De Francesco" <fabio.maria.de.francesco@linux.intel.com> wrote:
> Add cond_guard() macro to conditional guards and use it to replace an
> open-coded up_read() in show_targetN().
>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Suggested-by: Dan Williams <dan.j.williams@intel.com>
> Suggested-by: Ira Weiny <ira.weiny@intel.com>
Change log since RFC v5?
>
> Fabio M. De Francesco (2):
> cleanup: Add cond_guard() to conditional guards
> cxl/region: Use cond_guard() in show_targetN()
>
> drivers/cxl/core/region.c | 16 ++++------------
> include/linux/cleanup.h | 14 ++++++++++++++
> 2 files changed, 18 insertions(+), 12 deletions(-)
>
prev parent reply other threads:[~2024-02-05 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 17:31 [PATCH 0/2] Add cond_guard() to conditional guards Fabio M. De Francesco
2024-02-04 17:31 ` [PATCH 1/2] cleanup: " Fabio M. De Francesco
2024-02-05 11:09 ` Jonathan Cameron
2024-02-05 17:04 ` Ira Weiny
2024-02-05 19:13 ` Dan Williams
2024-02-04 17:31 ` [PATCH 2/2] cxl/region: Use cond_guard() in show_targetN() Fabio M. De Francesco
2024-02-05 11:11 ` Jonathan Cameron
2024-02-05 17:06 ` Ira Weiny
2024-02-05 10:56 ` Jonathan Cameron [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=20240205105606.00000546@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=fabio.maria.de.francesco@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.