From: Yuval Shaia <yuval.shaia@oracle.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: akpm@linux-foundation.org, tglx@linutronix.de,
keescook@chromium.org, pombredanne@nexb.com, bp@suse.de,
abbotti@mev.co.uk, rdunlap@infradead.org, bhe@redhat.com,
yamada.masahiro@socionext.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linux/kernel.h: Fix minor type in comment
Date: Tue, 10 Apr 2018 10:14:32 +0300 [thread overview]
Message-ID: <20180410071432.GA5093@yuvallap> (raw)
In-Reply-To: <20180410070626.u27zsu2kgkojax5l@gmail.com>
On Tue, Apr 10, 2018 at 09:06:26AM +0200, Ingo Molnar wrote:
>
> * Yuval Shaia <yuval.shaia@oracle.com> wrote:
>
> > Signed-off-by: Yuval Shaia <yuval.shaia@oracle.com>
> > ---
> > include/linux/kernel.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/linux/kernel.h b/include/linux/kernel.h
> > index ce51455e2adf..a5b4ba3bdb61 100644
> > --- a/include/linux/kernel.h
> > +++ b/include/linux/kernel.h
> > @@ -651,7 +651,7 @@ do { \
> > * your code. (Extra memory is used for special buffers that are
> > * allocated when trace_printk() is used.)
> > *
> > - * A little optization trick is done here. If there's only one
> > + * A little optimization trick is done here. If there's only one
> > * argument, there's no need to scan the string for printf formats.
> > * The trace_puts() will suffice. But how can we take advantage of
> > * using trace_puts() when trace_printk() has only one argument?
>
> Please also fix the typo in the title ;-)
Sorry, fixed that but forgot to amend :)
Will post v2 in few seconds.
>
> Thanks,
>
> Ingo
prev parent reply other threads:[~2018-04-10 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 6:57 [PATCH] linux/kernel.h: Fix minor type in comment Yuval Shaia
2018-04-10 7:06 ` Ingo Molnar
2018-04-10 7:14 ` Yuval Shaia [this message]
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=20180410071432.GA5093@yuvallap \
--to=yuval.shaia@oracle.com \
--cc=abbotti@mev.co.uk \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@suse.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pombredanne@nexb.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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