From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Juergen Gross <jgross@suse.com>, Jason Baron <jbaron@akamai.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] static_key: Improve uninizialized key warning
Date: Thu, 19 Oct 2017 07:33:27 +0200 [thread overview]
Message-ID: <20171019053327.526kfuuqopqlsg4o@gmail.com> (raw)
In-Reply-To: <20171018120816.75777573@gandalf.local.home>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 18 Oct 2017 12:06:59 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > > Signed-off-by: Borislav Petkov <bp@suse.de>
> > > Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>
> > > Cc: Ingo Molnar <mingo@kernel.org>
> > > Cc: Juergen Gross <jgross@suse.com>
> > > Cc: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
> >
> > Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> >
>
>
> Ingo, you may want to fix the typo in the subject "uninitialized".
Yeah, I also changed it to %pS to help debug arrays, or cases where somehow a
non-data symbol ends up being passed to it. Plus I changed the message from:
static_key_disable_cpuslocked, key virt_spin_lock_key used before call to jump_label_init.
to:
static_key_disable_cpuslocked() static key 'virt_spin_lock_key' used before call to jump_label_init()
to make it all obviously readable. I mean, what if the symbol is named 'key' and
we'd get confusing printouts like:
static_key_disable_cpuslocked, key key used before call to jump_label_init.
Plus functions should be referred to with () to disambiguate them from other
symbol names. Also, proper use of punctuation symbols.
Thanks,
Ingo
next prev parent reply other threads:[~2017-10-19 5:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 10:39 [PATCH] " Borislav Petkov
2017-10-18 11:15 ` Steven Rostedt
2017-10-18 13:19 ` Ingo Molnar
2017-10-18 13:27 ` Steven Rostedt
2017-10-18 15:24 ` [PATCH v2] " Borislav Petkov
2017-10-18 16:06 ` Steven Rostedt
2017-10-18 16:08 ` Steven Rostedt
2017-10-19 5:33 ` Ingo Molnar [this message]
2017-10-19 5:52 ` [tip:locking/core] locking/static_keys: Improve uninitialized " tip-bot for Borislav Petkov
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=20171019053327.526kfuuqopqlsg4o@gmail.com \
--to=mingo@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hannes@stressinduktion.org \
--cc=jbaron@akamai.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®