From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-usb@vger.kernel.org
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 1/2] thunderbolt: debugfs: Use DEBUGFS_MODE with path config space access
Date: Wed, 11 Nov 2026 13:32:47 +0100 [thread overview]
Message-ID: <20261111123248.1312997-1-mika.westerberg@linux.intel.com> (raw)
Commit 398da8e64321 ("thunderbolt: debugfs: Add write capability to path
config space") added write support to path config spaces but forgot to
update the mode accordingly. This fixes it to use correct mode via
DEBUGFS_MODE.
Fixes: 398da8e64321 ("thunderbolt: debugfs: Add write capability to path config space")
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
---
drivers/thunderbolt/debugfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thunderbolt/debugfs.c b/drivers/thunderbolt/debugfs.c
index 6a6875eb07ba..0d9f41a0f2cd 100644
--- a/drivers/thunderbolt/debugfs.c
+++ b/drivers/thunderbolt/debugfs.c
@@ -2519,7 +2519,7 @@ void tb_switch_debugfs_init(struct tb_switch *sw)
debugfs_dir = debugfs_create_dir(dir_name, sw->debugfs_dir);
debugfs_create_file("regs", DEBUGFS_MODE, debugfs_dir,
port, &port_regs_fops);
- debugfs_create_file("path", 0400, debugfs_dir, port,
+ debugfs_create_file("path", DEBUGFS_MODE, debugfs_dir, port,
&path_fops);
if (port->config.counters_support)
debugfs_create_file("counters", 0600, debugfs_dir, port,
--
2.50.1
next reply other threads:[~2026-11-11 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 12:32 Mika Westerberg [this message]
2026-11-11 12:32 ` [PATCH 2/2] thunderbolt: Return -ETIMEDOUT if XDomain peer returns ERROR_NOT_READY Mika Westerberg
2026-11-11 12:45 ` sashiko-bot
2026-11-11 12:42 ` [PATCH 1/2] thunderbolt: debugfs: Use DEBUGFS_MODE with path config space access sashiko-bot
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=20261111123248.1312997-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
/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.