From: yeyunfeng <yeyunfeng@huawei.com>
To: <tglx@linutronix.de>
Cc: <linux-kernel@vger.kernel.org>, <trivial@kernel.org>
Subject: [PATCH] genirq: modify the comment for irq_desc
Date: Mon, 2 Sep 2019 19:25:41 +0800 [thread overview]
Message-ID: <f31aba98-5abe-6719-1490-cb249cfe0f08@huawei.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2: 0001-genirq-modify-the-comment-for-irq_desc.patch --]
[-- Type: text/plain, Size: 1109 bytes --]
From 69f508e27f8eb41215c782509766fbf95f5c2a05 Mon Sep 17 00:00:00 2001
From: YunFeng Ye <yeyunfeng@huawei.com>
Date: Mon, 2 Sep 2019 15:19:57 +0800
Subject: [PATCH] genirq: modify the comment for irq_desc
commit 0c6f8a8b917a ("genirq: Remove compat code") deleted the @status
member of irq_desc, but forgot to update the comment.
Signed-off-by: YunFeng Ye <yeyunfeng@huawei.com>
---
include/linux/irqdesc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/irqdesc.h b/include/linux/irqdesc.h
index d6e2ab5..8f2820c 100644
--- a/include/linux/irqdesc.h
+++ b/include/linux/irqdesc.h
@@ -24,7 +24,7 @@
* @handle_irq: highlevel irq-events handler
* @preflow_handler: handler called before the flow handler (currently used by sparc)
* @action: the irq action chain
- * @status: status information
+ * @status_use_accessors: status information
* @core_internal_state__do_not_mess_with_it: core internal status information
* @depth: disable-depth, for nested irq_disable() calls
* @wake_depth: enable depth, for multiple irq_set_irq_wake() callers
--
1.8.3.1
next reply other threads:[~2019-09-02 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 11:25 yeyunfeng [this message]
2019-09-18 7:28 ` [PATCH] genirq: modify the comment for irq_desc Yunfeng Ye
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=f31aba98-5abe-6719-1490-cb249cfe0f08@huawei.com \
--to=yeyunfeng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=trivial@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;
as well as URLs for NNTP newsgroup(s).