public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ChengChaoChun <abc21531050@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: ChengChaoChun <abc21531050@gmail.com>
Subject: [PATCH] linux/interrupt.h: fix struct irqaction comment order inconsistency
Date: Tue,  9 Jul 2024 00:06:51 +0800	[thread overview]
Message-ID: <20240708160651.54239-1-abc21531050@gmail.com> (raw)

Rearrange struct irqaction comment to match member order in the code.

Signed-off-by: ChengChaoChun <abc21531050@gmail.com>
---
 include/linux/interrupt.h | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
index 5c9bdd3ffccc..b405e181829b 100644
--- a/include/linux/interrupt.h
+++ b/include/linux/interrupt.h
@@ -104,19 +104,19 @@ typedef irqreturn_t (*irq_handler_t)(int, void *);
 
 /**
  * struct irqaction - per interrupt action descriptor
- * @handler:	interrupt handler function
- * @name:	name of the device
- * @dev_id:	cookie to identify the device
- * @percpu_dev_id:	cookie to identify the device
- * @next:	pointer to the next irqaction for shared interrupts
- * @irq:	interrupt number
- * @flags:	flags (see IRQF_* above)
- * @thread_fn:	interrupt handler function for threaded interrupts
- * @thread:	thread pointer for threaded interrupts
- * @secondary:	pointer to secondary irqaction (force threading)
- * @thread_flags:	flags related to @thread
- * @thread_mask:	bitmask for keeping track of @thread activity
- * @dir:	pointer to the proc/irq/NN/name entry
+ * @handler:    interrupt handler function
+ * @dev_id:     cookie to identify the device
+ * @percpu_dev_id:      cookie to identify the device
+ * @next:       pointer to the next irqaction for shared interrupts
+ * @thread_fn:  interrupt handler function for threaded interrupts
+ * @thread:     thread pointer for threaded interrupts
+ * @secondary:  pointer to secondary irqaction (force threading)
+ * @irq:        interrupt number
+ * @flags:      flags (see IRQF_* above)
+ * @thread_flags:       flags related to @thread
+ * @thread_mask:        bitmask for keeping track of @thread activity
+ * @name:       name of the device
+ * @dir:        pointer to the proc/irq/NN/name entry
  */
 struct irqaction {
 	irq_handler_t		handler;
-- 
2.34.1


             reply	other threads:[~2024-07-08 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 16:06 ChengChaoChun [this message]
2024-07-26 16:33 ` [PATCH] linux/interrupt.h: fix struct irqaction comment order inconsistency Thomas Gleixner

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=20240708160651.54239-1-abc21531050@gmail.com \
    --to=abc21531050@gmail.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox