From: Greg KH <gregkh@linuxfoundation.org>
To: Germano Percossi <germano.percossi@citrix.com>
Cc: pshilov@microsoft.com, smfrench@gmail.com,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "CIFS: reconnect thread reschedule itself" has been added to the 4.10-stable tree
Date: Thu, 20 Apr 2017 13:05:25 +0200 [thread overview]
Message-ID: <20170420110525.GA26795@kroah.com> (raw)
In-Reply-To: <48f830fd-5d60-91bf-6185-bb5a3b476dfe@citrix.com>
On Thu, Apr 20, 2017 at 11:07:52AM +0100, Germano Percossi wrote:
> Hi Greg,
>
> With respect to the 3 patches I received notifications about,
> I noticed the following:
>
> a0918f1ce6 "CIFS: remove bad_network_name flag": you tried to apply it
> on 4.10, 4.9 and 4.4 but it failed. I sent the fixed backport.
> 1fa839b498 "CIFS: store results of cifs_reopen_file..": it has been
> put in the queue for 3.18, 4.4, 4.9 and 4.10
> 18ea43113f "CIFS: reconnect thread reschedule itself": it has been
> put in the queue for 4.9 and 4.10
>
> Is there any reason why 1fa839b498 goes into 4 stable releases, while
> the others in in, respectively, 3 and 2 releases?
Perhaps they do not apply to those trees? That's the reason I wouldn't
add them there. If you think they do belong there, I would be glad to
accept a backported version of the patches.
thanks,
greg k-h
next prev parent reply other threads:[~2017-04-20 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 12:48 Patch "CIFS: reconnect thread reschedule itself" has been added to the 4.10-stable tree gregkh
2017-04-20 10:07 ` Germano Percossi
2017-04-20 11:05 ` Greg KH [this message]
2017-04-20 11:10 ` Germano Percossi
2017-04-20 11:44 ` Greg KH
2017-04-20 13:07 ` Germano Percossi
2017-04-20 13:34 ` Greg KH
2017-04-21 8:37 ` Greg KH
2017-04-21 8:38 ` Greg KH
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=20170420110525.GA26795@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=germano.percossi@citrix.com \
--cc=pshilov@microsoft.com \
--cc=smfrench@gmail.com \
--cc=stable-commits@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).