From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 2/2] genirq: Fix trivia typo in the comment CPY ==> COPY
Date: Fri, 5 Apr 2024 21:56:46 +0300 [thread overview]
Message-ID: <20240405185726.3931703-3-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20240405185726.3931703-1-andriy.shevchenko@linux.intel.com>
IRQ_SET_MASK_NOCOPY is defined with 'O' letter. Fix the comment.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
include/linux/irq.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/irq.h b/include/linux/irq.h
index 97baa937ab5b..a217e1029c1d 100644
--- a/include/linux/irq.h
+++ b/include/linux/irq.h
@@ -115,7 +115,7 @@ enum {
* Return value for chip->irq_set_affinity()
*
* IRQ_SET_MASK_OK - OK, core updates irq_common_data.affinity
- * IRQ_SET_MASK_NOCPY - OK, chip did update irq_common_data.affinity
+ * IRQ_SET_MASK_NOCOPY - OK, chip did update irq_common_data.affinity
* IRQ_SET_MASK_OK_DONE - Same as IRQ_SET_MASK_OK for core. Special code to
* support stacked irqchips, which indicates skipping
* all descendant irqchips.
--
2.43.0.rc1.1.gbec44491f096
next prev parent reply other threads:[~2024-04-05 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 18:56 [PATCH v1 0/2] genirq: Update MAINTAINERS and trivia fix Andy Shevchenko
2024-04-05 18:56 ` [PATCH v1 1/2] genirq: Update MAINTAINERS to include IRQ related header files Andy Shevchenko
2024-04-11 10:33 ` [tip: irq/core] genirq: Update MAINTAINERS to include interrupt " tip-bot2 for Andy Shevchenko
2024-04-05 18:56 ` Andy Shevchenko [this message]
2024-04-11 10:33 ` [tip: irq/core] genirq: Fix trivial typo in the comment CPY ==> COPY tip-bot2 for Andy Shevchenko
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=20240405185726.3931703-3-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox