From: Greg KH <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org,
"# v4 . 13" <stable@vger.kernel.org>
Subject: Re: [PATCH] ovl: handle ENOENT on index lookup
Date: Fri, 20 Oct 2017 13:37:12 +0200 [thread overview]
Message-ID: <20171020113712.GB699@kroah.com> (raw)
In-Reply-To: <1508497270-27971-1-git-send-email-amir73il@gmail.com>
On Fri, Oct 20, 2017 at 02:01:10PM +0300, Amir Goldstein wrote:
> Fixes: 359f392ca53e ("ovl: lookup index entry for copy up origin")
> Cc: <stable@vger.kernel.org> # v4.13
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Why is there no changelog at all? Not good, especially for a patch
wanting to be sent to the stable trees :(
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-20 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 11:01 [PATCH] ovl: handle ENOENT on index lookup Amir Goldstein
2017-10-20 11:37 ` Greg KH [this message]
2017-10-20 11:42 ` Amir Goldstein
2017-10-20 13:23 ` Miklos Szeredi
2017-10-20 14:21 ` Amir Goldstein
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=20171020113712.GB699@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stable@vger.kernel.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