From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Stable <stable@vger.kernel.org>
Subject: Re: request for 4.14-stable: b54e41f5efcb ("udf: Allow mounting volumes with incorrect identification strings")
Date: Thu, 6 Dec 2018 11:54:48 +0100 [thread overview]
Message-ID: <20181206105448.GI19891@kroah.com> (raw)
In-Reply-To: <CADVatmMSaP3FFTEbyJh7n0jLECO0KRXUtK0nmMccYA9CJ3D_AQ@mail.gmail.com>
On Wed, Dec 05, 2018 at 11:54:10AM +0000, Sudip Mukherjee wrote:
> On Wed, Dec 5, 2018 at 11:30 AM Jan Kara <jack@suse.cz> wrote:
> >
> > Hi,
> >
> > On Tue 04-12-18 20:53:47, Sudip Mukherjee wrote:
> > > This has been applied to 4.19-stable, but should be needed in
> > > 4.14-stable also. I have attached the backported patch and have
> > > also tested with one such DVD where the problem was seen.
> >
> > Thanks for the backport. I actually didn't get a message that application
> > of this patch to 4.14-stable would fail so probably it is just waiting in
> > Greg's queue. Anyway the patch looks good to me.
>
> I was also wondering about that. But usually Greg's script will try
> the commits marked for stable on all the LTS kernels at the same time.
> So since it is applied to 4.19-stable, his script should have already
> tried in 4.14-stable (unless he has changed his scripts after last
> time I saw it).
I don't know what went wrong here, my fault, sorry.
Yes, this didn't apply to the older kernels and it should have triggered
an email from me.
greg k-h
next prev parent reply other threads:[~2018-12-06 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 20:53 request for 4.14-stable: b54e41f5efcb ("udf: Allow mounting volumes with incorrect identification strings") Sudip Mukherjee
2018-12-05 11:30 ` Jan Kara
2018-12-05 11:54 ` Sudip Mukherjee
2018-12-06 10:54 ` Greg Kroah-Hartman [this message]
2018-12-06 10:56 ` Greg Kroah-Hartman
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=20181206105448.GI19891@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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).