From: Mario Limonciello <mario.limonciello@amd.com>
To: Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>
Cc: <anson.tsao@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
"Sanju Mehta" <Sanju.Mehta@amd.com>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2] thunderbolt: Use const qualifier for `ring_interrupt_index`
Date: Fri, 10 Mar 2023 11:20:49 -0600 [thread overview]
Message-ID: <20230310172050.1394-2-mario.limonciello@amd.com> (raw)
In-Reply-To: <20230310172050.1394-1-mario.limonciello@amd.com>
`ring_interrupt_index` doesn't change the data for `ring` so
mark it as const.
Cc: Sanju Mehta <Sanju.Mehta@amd.com>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
drivers/thunderbolt/nhi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thunderbolt/nhi.c b/drivers/thunderbolt/nhi.c
index 4dce2edd86ea0..fdc0c3ba2ef01 100644
--- a/drivers/thunderbolt/nhi.c
+++ b/drivers/thunderbolt/nhi.c
@@ -46,7 +46,7 @@
#define QUIRK_AUTO_CLEAR_INT BIT(0)
#define QUIRK_E2E BIT(1)
-static int ring_interrupt_index(struct tb_ring *ring)
+static int ring_interrupt_index(const struct tb_ring *ring)
{
int bit = ring->hop;
if (!ring->is_tx)
--
2.25.1
next prev parent reply other threads:[~2023-03-10 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:20 [PATCH 0/2] Fix TX/RX interrupt handling Mario Limonciello
2023-03-10 17:20 ` Mario Limonciello [this message]
2023-03-10 17:20 ` [PATCH 2/2] thunderbolt: Disable interrupt auto clear for rings Mario Limonciello
2023-03-13 5:46 ` Mika Westerberg
2023-03-14 14:28 ` [PATCH 0/2] Fix TX/RX interrupt handling Mika Westerberg
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=20230310172050.1394-2-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=Sanju.Mehta@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=anson.tsao@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®