From: Steven Rostedt <rostedt@goodmis.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH v1] tracing: Trivia spelling fix containerof() -> container_of()
Date: Tue, 24 Jul 2018 10:58:44 -0400 [thread overview]
Message-ID: <20180724105844.0ce62f1e@gandalf.local.home> (raw)
In-Reply-To: <20180723083159.82112-1-andriy.shevchenko@linux.intel.com>
On Mon, 23 Jul 2018 11:31:59 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> This is the only location on kernel that has wrong spelling
> of the container_of() helper. Fix it.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
> ---
> kernel/trace/trace_printk.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace_printk.c b/kernel/trace/trace_printk.c
> index 50f44b7b2b32..3cd7b0fcacc6 100644
> --- a/kernel/trace/trace_printk.c
> +++ b/kernel/trace/trace_printk.c
> @@ -114,7 +114,7 @@ static int module_trace_bprintk_format_notify(struct notifier_block *self,
> * section, then we need to read the link list pointers. The trick is
> * we pass the address of the string to the seq function just like
> * we do for the kernel core formats. To get back the structure that
> - * holds the format, we simply use containerof() and then go to the
> + * holds the format, we simply use container_of() and then go to the
> * next format in the list.
> */
> static const char **
prev parent reply other threads:[~2018-07-24 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 8:31 [PATCH v1] tracing: Trivia spelling fix containerof() -> container_of() Andy Shevchenko
2018-07-24 14:58 ` Steven Rostedt [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=20180724105844.0ce62f1e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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).