From: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
To: Tejun Heo <tj@kernel•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: Fri, 17 Mar 2017 10:25:53 +0900 [thread overview]
Message-ID: <20170317012553.GA31878@kroah.com> (raw)
In-Reply-To: <20170316211430.GC1480@htj.duckdns.org>
On Thu, Mar 16, 2017 at 05:14:30PM -0400, Tejun Heo wrote:
> 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.
Ok, will take it in my tree, thanks.
greg k-h
next prev parent reply other threads:[~2017-03-17 1:26 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
2017-03-17 1:25 ` Greg Kroah-Hartman [this message]
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=20170317012553.GA31878@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=fbarrat@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=tj@kernel$(echo .)org \
--cc=vaibhav@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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