From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: jpoimboe@redhat.com, jbaron@akamai.com, ardb@kernel.org,
linux-kernel@vger.kernel.org, ltykernel@gmail.com
Subject: Re: [PATCH] static_call: Update comment
Date: Thu, 5 Aug 2021 12:07:43 -0400 [thread overview]
Message-ID: <20210805120743.0fb8832d@oasis.local.home> (raw)
In-Reply-To: <YQwIorQBHEq+s73b@hirez.programming.kicks-ass.net>
On Thu, 5 Aug 2021 17:49:54 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> Update the comment with the new features.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
next prev parent reply other threads:[~2021-08-05 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 15:49 [PATCH] static_call: Update comment Peter Zijlstra
2021-08-05 16:07 ` Steven Rostedt [this message]
2021-08-08 18:47 ` Josh Poimboeuf
2021-08-17 20:13 ` [tip: locking/core] static_call: Update API documentation tip-bot2 for Peter Zijlstra
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=20210805120743.0fb8832d@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=ardb@kernel.org \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltykernel@gmail.com \
--cc=peterz@infradead.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).