From: Tejun Heo <tj@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Frederic Barrat <fbarrat@linux.vnet.ibm.com>
Subject: Re: [PATCH] kernfs: Check KERNFS_HAS_RELEASE before calling kernfs_release_file()
Date: Thu, 16 Mar 2017 17:14:30 -0400 [thread overview]
Message-ID: <20170316211430.GC1480@htj.duckdns.org> (raw)
In-Reply-To: <20170314030829.GA26049@kroah.com>
Hello, Greg.
On Tue, Mar 14, 2017 at 11:08:29AM +0800, Greg Kroah-Hartman wrote:
> Tejun, want to take this through your tree, or at the least, give me an
> ack for this?
Just acked. I think going through your tree is better for this one.
Thanks!
--
tejun
next prev parent reply other threads:[~2017-03-16 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 2:47 [PATCH] kernfs: Check KERNFS_HAS_RELEASE before calling kernfs_release_file() Vaibhav Jain
2017-03-14 3:08 ` Greg Kroah-Hartman
2017-03-16 21:14 ` Tejun Heo [this message]
2017-03-17 1:25 ` Greg Kroah-Hartman
2017-03-16 21:13 ` Tejun Heo
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=20170316211430.GC1480@htj.duckdns.org \
--to=tj@kernel.org \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vaibhav@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).