All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hanjun Guo <guohanjun@huawei.com>
Cc: stable@vger.kernel.org, will.deacon@arm.com, sasha.levin@oracle.com
Subject: Re: [PATCH 0/3] Candidate ARM64 stable patches for linux-4.1.y
Date: Sun, 14 Feb 2016 17:44:38 -0800	[thread overview]
Message-ID: <20160215014438.GA30806@kroah.com> (raw)
In-Reply-To: <56C12B6C.4040506@huawei.com>

On Mon, Feb 15, 2016 at 09:35:40AM +0800, Hanjun Guo wrote:
> On 2016/2/15 5:00, Greg KH wrote:
> > On Tue, Feb 02, 2016 at 12:06:44PM +0800, Hanjun Guo wrote:
> >> From: Hanjun Guo <hanjun.guo@linaro.org>
> >>
> >> Hi Greg,
> > I'm no longer dealing with 4.1 stable things, sorry.
> >
> 
> Sorry, I didn't notice this when I was sending out this patch set,
> should I resend this to Sasha (with Sasha in the cc list)?

Don't know, that's up to Sasha :)

  reply	other threads:[~2016-02-15  1:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  4:06 [PATCH 0/3] Candidate ARM64 stable patches for linux-4.1.y Hanjun Guo
2016-02-02  4:06 ` [PATCH 1/3] arm64: fix missing syscall trace exit Hanjun Guo
2016-02-02  4:06 ` [PATCH 2/3] arm64: entry: always restore x0 from the stack on syscall return Hanjun Guo
2016-02-02  4:06 ` [PATCH 3/3] arm64: mm: ensure patched kernel text is fetched from PoU Hanjun Guo
2016-02-14 21:00   ` Greg KH
2016-02-15  1:43     ` Hanjun Guo
2016-02-14 21:00 ` [PATCH 0/3] Candidate ARM64 stable patches for linux-4.1.y Greg KH
2016-02-15  1:35   ` Hanjun Guo
2016-02-15  1:44     ` Greg KH [this message]
2016-02-16  5:59       ` Hanjun Guo
2016-02-16  6:09         ` Sasha Levin

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=20160215014438.GA30806@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=guohanjun@huawei.com \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.org \
    --cc=will.deacon@arm.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 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.