From: Sasha Levin <sashal@kernel.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
joe@perches.com, tglx@linutronix.de,
Marc Zyngier <maz@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Request to backport "irqchip/gic-v3-its: Fix misuse of GENMASK macro"
Date: Fri, 28 Feb 2020 22:08:38 -0500 [thread overview]
Message-ID: <20200229030838.GE21491@sasha-vm> (raw)
In-Reply-To: <47617046-53ba-ed7f-ccbb-5c7c09426552@huawei.com>
On Fri, Feb 28, 2020 at 02:50:51PM +0800, Zenghui Yu wrote:
>Hi Greg, Sasha,
>
>Could you please help to backport the upstream commit
>20faba848752901de23a4d45a1174d64d2069dde ("irqchip/gic-v3-its: Fix
>misuse of GENMASK macro") to the stable linux-4.19 tree since it's
>definitely a fix for 4.19. Note that it's not needed for other stable
>trees.
>
>I've tried and it can be applied to 4.19.106 cleanly.
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-29 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 6:50 Request to backport "irqchip/gic-v3-its: Fix misuse of GENMASK macro" Zenghui Yu
2020-02-29 3:08 ` Sasha Levin [this message]
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=20200229030838.GE21491@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yuzenghui@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).