From: Daniel Borkmann <daniel@iogearbox.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: viro@ZenIV.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracefs, debugfs: fix refcount imbalance in start_creating
Date: Wed, 04 Nov 2015 23:23:44 +0100 [thread overview]
Message-ID: <563A8570.8070309@iogearbox.net> (raw)
In-Reply-To: <20151102140739.6e0d0d46@gandalf.local.home>
On 11/02/2015 08:07 PM, Steven Rostedt wrote:
> On Fri, 9 Oct 2015 20:30:10 +0200
> Daniel Borkmann <daniel@iogearbox.net> wrote:
>
[...]
>>
>> Fixes: 4282d60689d4 ("tracefs: Add new tracefs file system")
>> Fixes: 190afd81e4a5 ("debugfs: split the beginning and the end of __create_file() off")
>> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
>> Cc: Steven Rostedt <rostedt@goodmis.org>
[...]
Fyi, I'll respin and split this one into two, so they can be routed through
their individual trees. (Keeping Steven's Acked-by on the tracefs one.)
Thanks & sorry for the noise,
Daniel
prev parent reply other threads:[~2015-11-04 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 18:30 [PATCH] tracefs, debugfs: fix refcount imbalance in start_creating Daniel Borkmann
2015-11-02 19:07 ` Steven Rostedt
2015-11-04 22:23 ` Daniel Borkmann [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=563A8570.8070309@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=viro@ZenIV.linux.org.uk \
/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