From: Anna Schumaker <Anna.Schumaker@Netapp.com>
To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>,
Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: patch to candidate for stable kernel 4.10
Date: Tue, 11 Apr 2017 15:25:32 -0400 [thread overview]
Message-ID: <1dab6e33-abef-5d64-3974-df27e5fbda15@Netapp.com> (raw)
In-Reply-To: <2D071154-2E1F-4C43-95EA-00C4BBAFD4FA@desy.de>
Sounds good to me! Sorry that my initial pull request didn't have "cc: stable" added to it...
Anna
On 04/09/2017 04:14 PM, Mkrtchyan, Tigran wrote:
> The problem was introduced in 4.10.
>
> Anna, can you comment?
>
>
> -Tigran
>
> ----- Reply message -----
> From: "Greg KH" <gregkh@linuxfoundation.org>
> To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>, "Anna Schumaker" <Anna.Schumaker@Netapp.com>
> Cc: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
> Subject: patch to candidate for stable kernel 4.10
> Date: Sun, Apr 9, 2017 21:14
>
>
> On Sun, Apr 09, 2017 at 11:36:30AM +0200, Mkrtchyan, Tigran wrote:
>>
>> Dear stable kernel maintainers,
>>
>> Please consider commit
>>
>> f17f8a14e82cdf34cd6473e3644f3c672b3884f6
>>
>> to be included into 4.10 kernel. As long as it crashes
>> kernels used by some distors, we have to disable corresponding
>> functionality on the NFS servers.
>
> So just for 4.10? Nothing older?
>
> What does the NFS maintainer say?
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2017-04-11 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 9:36 patch to candidate for stable kernel 4.10 Mkrtchyan, Tigran
2017-04-09 19:14 ` Greg KH
[not found] ` <2D071154-2E1F-4C43-95EA-00C4BBAFD4FA@desy.de>
2017-04-11 19:25 ` Anna Schumaker [this message]
2017-04-12 13:12 ` 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=1dab6e33-abef-5d64-3974-df27e5fbda15@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
/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