All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:34:19 +0200	[thread overview]
Message-ID: <20170420133419.GC8998@kroah.com> (raw)
In-Reply-To: <ce86148a-a25c-21cd-923b-3c211c6ebc8e@citrix.com>

On Thu, Apr 20, 2017 at 02:07:47PM +0100, Germano Percossi wrote:
> Hi,
> 
> On 20/04/17 12:44, Greg KH wrote:
> > On Thu, Apr 20, 2017 at 12:10:00PM +0100, Germano Percossi wrote:
> > > The reason why I asked it's because I did not receive any
> > > "Failed" notification, so I assumed you did not even try.
> > 
> > I tried, but for patches without any specific "Fixes:" tag, I have to
> > just guess that if the patch does not apply, then it was not wanted
> > to go that far back.
> > 
> 
> You were right in your assumption about 18ea43113f: it could be ported
> but it is not so important for 3.18 and 4.4 because we are not using
> persistent handles there.
> 
> For what concerns a0918f1ce6 "remove bad network.." on 3.18 I just ran
> git cherry-pick a0918f1ce6
> on stable/linux-3.18.y without any problem.
> Unless you use other commands with fuzz level lower than 2
> it should apply as is.

Odd, it does apply, thanks.  I'll apply it for the next 3.18-stable
release after the current -rc one is released in a few days.

thanks for researching this.

greg k-h

  reply	other threads:[~2017-04-20 13:34 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
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 [this message]
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=20170420133419.GC8998@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.