All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weilong Chen <chenweilong@huawei.com>
To: Rusty Russell <rusty@rustcorp.com.au>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, Jessica Yu <jeyu@redhat.com>
Subject: Re: FAILED: patch "[PATCH] modules: fix longstanding /proc/kallsyms vs module insertion" failed to apply to 4.4-stable tree
Date: Tue, 8 Mar 2016 16:34:39 +0800	[thread overview]
Message-ID: <56DE8E9F.601@huawei.com> (raw)
In-Reply-To: <8760wxms0i.fsf@rustcorp.com.au>

Hi
Can this patch be add to stable-3.10.y?
Actually we got the bug on it.

Thanks!

On 2016/3/8 13:57, Rusty Russell wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
>> On Sun, Mar 06, 2016 at 03:35:37PM +1030, Rusty Russell wrote:
>>> gregkh@linuxfoundation.org writes:
>>>
>>>> The patch below does not apply to the 4.4-stable tree.
>>>> If someone wants it applied there, or to any other stable or longterm
>>>> tree, then please email the backport, including the original git commit
>>>> id to <stable@vger.kernel.org>.
>>>
>>> Rebased.  Fairly trivial, but CC'd Jessica in case she wants to
>>> double-check my work.
>>
>> Thanks, I've queued this up for 4.4-stable.  Should it go to any older
>> kernels as well?
>
> Yes, definitely, but this version should apply to them with minimal fuss.
>
> Thanks,
> Rusty.
>
> .
>


  reply	other threads:[~2016-03-08  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  2:41 FAILED: patch "[PATCH] modules: fix longstanding /proc/kallsyms vs module insertion" failed to apply to 4.4-stable tree gregkh
2016-03-06  5:05 ` Rusty Russell
2016-03-07 23:43   ` Greg KH
2016-03-08  5:57     ` Rusty Russell
2016-03-08  8:34       ` Weilong Chen [this message]
2016-03-13  4:54         ` Greg KH
2016-03-08  4:17   ` Jessica Yu

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=56DE8E9F.601@huawei.com \
    --to=chenweilong@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeyu@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --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.