From: Will Deacon <will@kernel.org>
To: vladimir.murzin@arm.com, matthias.bgg@gmail.com, maz@kernel.org,
james.morse@arm.com, corbet@lwn.net, selindag@gmail.com,
sashal@kernel.org, mark.rutland@arm.com, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org, ebiederm@xmission.com,
linux-kernel@vger.kernel.org,
Pavel Tatashin <pasha.tatashin@soleen.com>,
tyhicks@linux.microsoft.com, rfontana@redhat.com,
jmorris@namei.org, steve.capper@arm.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH 0/1] arm64/hibernate: sparse warnings fix
Date: Mon, 1 Feb 2021 17:13:24 +0000 [thread overview]
Message-ID: <161219505105.3603742.9530959766797999831.b4-ty@kernel.org> (raw)
In-Reply-To: <20210201150306.54099-1-pasha.tatashin@soleen.com>
On Mon, 1 Feb 2021 10:03:05 -0500, Pavel Tatashin wrote:
> This is against for-next/kexec, fix for sparse warning that was reported by
> kernel test robot [1].
>
> [1] https://lore.kernel.org/linux-arm-kernel/202101292143.C6TcKvvX-lkp@intel.com
>
> Pavel Tatashin (1):
> arm64: hibernate: add __force attribute to gfp_t casting
>
> [...]
Applied to arm64 (for-next/kexec), thanks!
[1/1] arm64: hibernate: add __force attribute to gfp_t casting
https://git.kernel.org/arm64/c/d1bbc35fcab2
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-02-01 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 15:03 [PATCH 0/1] arm64/hibernate: sparse warnings fix Pavel Tatashin
2021-02-01 15:03 ` [PATCH 1/1] arm64: hibernate: add __force attribute to gfp_t casting Pavel Tatashin
2021-02-02 8:42 ` Christoph Hellwig
2021-02-02 15:05 ` Pavel Tatashin
2021-02-01 17:13 ` Will Deacon [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=161219505105.3603742.9530959766797999831.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=james.morse@arm.com \
--cc=jmorris@namei.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=rfontana@redhat.com \
--cc=sashal@kernel.org \
--cc=selindag@gmail.com \
--cc=steve.capper@arm.com \
--cc=tyhicks@linux.microsoft.com \
--cc=vladimir.murzin@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 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).