The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: ChengChaoChun <abc21531050@gmail.com>
To: tglx@linutronix.de
Cc: rafael.j.wysocki@intel.com, frederic@kernel.org,
	joel@joelfernandes.org, dmitry.torokhov@gmail.com,
	yury.norov@gmail.com, linux-kernel@vger.kernel.org,
	abc21531050@gmail.com
Subject: [PATCH] Fix struct irqaction comment order inconsistency
Date: Mon, 12 Aug 2024 19:54:24 +0800	[thread overview]
Message-ID: <20240812115424.4748-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 | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
index 3f30c88e0b4c..ba59ae4521c9 100644
--- a/include/linux/interrupt.h
+++ b/include/linux/interrupt.h
@@ -105,19 +105,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
+ * @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
- * @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)
+ * @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
- * @dir:	pointer to the proc/irq/NN/name entry
+ * @name:		name of the device
+ * @dir:		pointer to the proc/irq/NN/name entry
  */
 struct irqaction {
 	irq_handler_t		handler;

base-commit: 7c626ce4bae1ac14f60076d00eafe71af30450ba
-- 
2.34.1


                 reply	other threads:[~2024-08-12 11:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240812115424.4748-1-abc21531050@gmail.com \
    --to=abc21531050@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tglx@linutronix.de \
    --cc=yury.norov@gmail.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