public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Zxyan Zhu <zxyan20@163.com>
Cc: broonie@kernel.org, rafael@kernel.org, dakr@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: debugfs: Fix name collision without atomic operations
Date: Tue, 4 Mar 2025 15:10:51 +0100	[thread overview]
Message-ID: <2025030418-pucker-flypaper-abac@gregkh> (raw)
In-Reply-To: <20250304122221.3317232-1-zxyan20@163.com>

On Tue, Mar 04, 2025 at 08:22:21PM +0800, Zxyan Zhu wrote:
> A global variable caused debugfs name conflicts during re-entry,

What global variable?

> leading to creation failures. Use atomic operations to ensure safe
> and unique naming.

Naming of what, the variables or the debugfs file?

confused,

greg k-h

      parent reply	other threads:[~2025-03-04 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 12:22 [PATCH] regmap: debugfs: Fix name collision without atomic operations Zxyan Zhu
2025-03-04 13:23 ` Mark Brown
2025-03-04 14:10 ` Greg KH [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=2025030418-pucker-flypaper-abac@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=zxyan20@163.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