All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng.Zhang@synaptics.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [4.14.y] request commit 94a5d8790e79 ("arm64: cpu_errata: include required headers")
Date: Tue, 11 Sep 2018 17:00:30 +0800	[thread overview]
Message-ID: <20180911170030.650928d8@xhacker.debian> (raw)

Hi Greg,

I think we missed the commit 94a5d8790e79 ("arm64: cpu_errata: include
required headers"), could you please include it in next stable release?

Thanks,
Jisheng

WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org,
	Arnd Bergmann <arnd@arndb.de>
Subject: [4.14.y] request commit 94a5d8790e79 ("arm64: cpu_errata: include required headers")
Date: Tue, 11 Sep 2018 17:00:30 +0800	[thread overview]
Message-ID: <20180911170030.650928d8@xhacker.debian> (raw)

Hi Greg,

I think we missed the commit 94a5d8790e79 ("arm64: cpu_errata: include
required headers"), could you please include it in next stable release?

Thanks,
Jisheng

             reply	other threads:[~2018-09-11  9:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  9:00 Jisheng Zhang [this message]
2018-09-11  9:00 ` [4.14.y] request commit 94a5d8790e79 ("arm64: cpu_errata: include required headers") Jisheng Zhang
2018-09-13  7:12 ` Greg Kroah-Hartman
2018-09-13  7:12   ` Greg Kroah-Hartman
2018-09-13  7:24   ` Jisheng Zhang
2018-09-13  7:24     ` Jisheng Zhang
2018-09-13  7:33     ` Jisheng Zhang
2018-09-13  7:33       ` Jisheng Zhang
2018-09-13  7:38     ` Greg Kroah-Hartman
2018-09-13  7:38       ` Greg Kroah-Hartman
2018-09-13  7:40       ` Arnd Bergmann
2018-09-13  7:40         ` Arnd Bergmann

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=20180911170030.650928d8@xhacker.debian \
    --to=jisheng.zhang@synaptics.com \
    --cc=linux-arm-kernel@lists.infradead.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.