From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH] printk: kmsg_dump: Mark registered flag as private
Date: Sun, 10 Mar 2019 21:03:02 +0100 [thread overview]
Message-ID: <20190310200302.GA11096@darwi-home-pc> (raw)
The 'registered' flag is internally used by kmsg_dump_register()
and kmsg_dump_unregister() to track multiple registrations of the
same dumper.
It's protected by printk's internal dump_list_lock, and must thus
be accessed only from there. Mark it as private.
Signed-off-by: Ahmed S. Darwish <darwish.07@gmail.com>
---
include/linux/kmsg_dump.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/kmsg_dump.h b/include/linux/kmsg_dump.h
index 2e7a1e032c71..7c08cb58259a 100644
--- a/include/linux/kmsg_dump.h
+++ b/include/linux/kmsg_dump.h
@@ -36,7 +36,7 @@ enum kmsg_dump_reason {
* @dump: Call into dumping code which will retrieve the data with
* through the record iterator
* @max_reason: filter for highest reason number that should be dumped
- * @registered: Flag that specifies if this is already registered
+ * @registered: Flag that specifies if this is already registered (private)
*/
struct kmsg_dumper {
struct list_head list;
--
2.21.0
next reply other threads:[~2019-03-10 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 20:03 Ahmed S. Darwish [this message]
2019-03-11 12:49 ` [PATCH] printk: kmsg_dump: Mark registered flag as private Sergey Senozhatsky
2019-03-12 9:18 ` Petr Mladek
2019-03-12 9:34 ` Sergey Senozhatsky
2019-03-12 20:05 ` Ahmed S. Darwish
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=20190310200302.GA11096@darwi-home-pc \
--to=darwish.07@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@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