From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Min-Hua Chen <minhuadotchen@gmail.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
kernel test robot <lkp@intel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/mm: mark private VM_FAULT_X defines as vm_fault_t
Date: Tue, 16 May 2023 16:14:41 +0100 [thread overview]
Message-ID: <168424504378.603922.13211388957168018213.b4-ty@kernel.org> (raw)
In-Reply-To: <20230502151909.128810-1-minhuadotchen@gmail.com>
On Tue, 2 May 2023 23:19:06 +0800, Min-Hua Chen wrote:
> This patch fixes several sparse warnings for fault.c:
>
> arch/arm64/mm/fault.c:493:24: sparse: warning: incorrect type in return expression (different base types)
> arch/arm64/mm/fault.c:493:24: sparse: expected restricted vm_fault_t
> arch/arm64/mm/fault.c:493:24: sparse: got int
> arch/arm64/mm/fault.c:501:32: sparse: warning: incorrect type in return expression (different base types)
> arch/arm64/mm/fault.c:501:32: sparse: expected restricted vm_fault_t
> arch/arm64/mm/fault.c:501:32: sparse: got int
> arch/arm64/mm/fault.c:503:32: sparse: warning: incorrect type in return expression (different base types)
> arch/arm64/mm/fault.c:503:32: sparse: expected restricted vm_fault_t
> arch/arm64/mm/fault.c:503:32: sparse: got int
> arch/arm64/mm/fault.c:511:24: sparse: warning: incorrect type in return expression (different base types)
> arch/arm64/mm/fault.c:511:24: sparse: expected restricted vm_fault_t
> arch/arm64/mm/fault.c:511:24: sparse: got int
> arch/arm64/mm/fault.c:670:13: sparse: warning: restricted vm_fault_t degrades to integer
> arch/arm64/mm/fault.c:670:13: sparse: warning: restricted vm_fault_t degrades to integer
> arch/arm64/mm/fault.c:713:39: sparse: warning: restricted vm_fault_t degrades to integer
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/mm: mark private VM_FAULT_X defines as vm_fault_t
https://git.kernel.org/arm64/c/d91d58087806
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-05-16 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 15:19 Min-Hua Chen
2023-05-16 15:14 ` 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=168424504378.603922.13211388957168018213.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=minhuadotchen@gmail.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
all inboxes | Powered by JetHome®