From: Alison Schofield <alison.schofield@intel.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Dan Williams <djbw@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>, <linux-kernel@vger.kernel.org>,
Peng Fan <peng.fan@nxp.com>, <nvdimm@lists.linux.dev>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH] dax: use assign_bit() where applicable
Date: Wed, 7 Oct 2026 19:02:02 -0700 [thread overview]
Message-ID: <asb5mkEpbCT9I8EF@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260919130750.3041470-1-peng.fan@oss.nxp.com>
On Sat, Sep 19, 2026 at 09:07:50PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Convert open-coded if/else with set_bit/clear_bit to the assign_bit API.
NAK
See also:
https://lore.kernel.org/lkml/asb3hGpSWVQk93cX@aschofie-mobl2.lan/
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> drivers/dax/super.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/dax/super.c b/drivers/dax/super.c
> index 45f84b0eb909..60c4aec52ae1 100644
> --- a/drivers/dax/super.c
> +++ b/drivers/dax/super.c
> @@ -385,10 +385,7 @@ EXPORT_SYMBOL_GPL(dax_flush);
>
> void dax_write_cache(struct dax_device *dax_dev, bool wc)
> {
> - if (wc)
> - set_bit(DAXDEV_WRITE_CACHE, &dax_dev->flags);
> - else
> - clear_bit(DAXDEV_WRITE_CACHE, &dax_dev->flags);
> + assign_bit(DAXDEV_WRITE_CACHE, &dax_dev->flags, wc);
> }
> EXPORT_SYMBOL_GPL(dax_write_cache);
>
> --
> 2.51.0
>
>
prev parent reply other threads:[~2026-10-08 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 13:07 [PATCH] dax: use assign_bit() where applicable Peng Fan (OSS)
2026-09-21 8:24 ` Gupta, Pankaj
2026-09-21 23:08 ` Jonathan Cameron
2026-10-08 1:59 ` Alison Schofield
2026-10-08 3:00 ` Peng Fan
2026-09-21 23:10 ` Dave Jiang
2026-10-08 2:02 ` Alison Schofield [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=asb5mkEpbCT9I8EF@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=djbw@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=vishal.l.verma@intel.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 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.