From: Steven Rostedt <rostedt@goodmis.org>
To: Chunyan Zhang <zhang.chunyan@linaro.org>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel: trace: pass export pointer as argument to ->write()
Date: Mon, 4 Dec 2017 07:09:38 -0500 [thread overview]
Message-ID: <20171204070938.552afb98@vmware.local.home> (raw)
In-Reply-To: <20170517225228.207c8d4e@gandalf.local.home>
On Wed, 17 May 2017 22:52:28 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 18 May 2017 10:26:59 +0800
> Chunyan Zhang <zhang.chunyan@linaro.org> wrote:
>
> > On 17 May 2017 at 16:05, Felipe Balbi <felipe.balbi@linux.intel.com> wrote:
> > > That way, users don't need to keep a global static pointer and can
> > > rely on container_of() to fetch their own structure.
> > >
> > > Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
> >
> > Reviewed-by: Chunyan Zhang <zhang.chunyan@linaro.org>
>
>
> If someone wants to pull this through their tree, feel free to do
> so. I've already acked it.
I guess nobody pulled this in. Does it still need to go? I'll add it to
my tree and start testing it, but I'll drop it if it's not needed (or I
don't get a response to this email).
-- Steve
next prev parent reply other threads:[~2017-12-04 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 8:05 [PATCH] kernel: trace: pass export pointer as argument to ->write() Felipe Balbi
2017-05-17 13:43 ` Steven Rostedt
2017-05-18 2:26 ` Chunyan Zhang
2017-05-18 2:52 ` Steven Rostedt
2017-12-04 12:09 ` Steven Rostedt [this message]
[not found] ` <20171204122312.tyxq54jmy7vijlmo@ukko.fi.intel.com>
2017-12-08 10:46 ` Felipe Balbi
2017-05-18 11:10 ` kbuild test robot
2017-06-02 10:14 ` Felipe Balbi
2017-06-02 10:20 ` [PATCH v2] " Felipe Balbi
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=20171204070938.552afb98@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=zhang.chunyan@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.