From: Andrew Morton <akpm@linux-foundation.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, x86@kernel.org,
linux-kernel@vger.kernel.org, willy@infradead.org
Subject: Re: [PATCH v2] x86/mm/fault.c: Convert to use vm_fault_t
Date: Wed, 9 Jan 2019 10:42:11 -0800 [thread overview]
Message-ID: <20190109104211.ce93b844df26c340100cfa14@linux-foundation.org> (raw)
In-Reply-To: <20190109183742.GA24326@jordon-HP-15-Notebook-PC>
On Thu, 10 Jan 2019 00:07:42 +0530 Souptick Joarder <jrdr.linux@gmail.com> wrote:
> Convert to use vm_fault_t type for last argument of do_sigbus().
>
> kbuild reported a warning during testing of final vm_fault_t patch
> integrated in mm tree.
Please be more specific when identifying patches.
> [auto build test WARNING on linus/master]
> [also build test WARNING on v5.0-rc1 next-20190109]
> [if your patch is applied to the wrong git tree, please drop us a note
> to help improve the system]
>
> https://github.com/0day-ci/linux/commits/Souptick-Joarder/
> mm-Create-the-new-vm_fault_t-type/20190109-154216
>
> All warnings:
>
> arch/x86/mm/fault.c:1051:39: warning: restricted vm_fault_t degrades to integer
> arch/x86/mm/fault.c:1057:29: warning: restricted vm_fault_t degrades to integer
> arch/x86/mm/fault.c:1059:29: warning: restricted vm_fault_t degrades to integer
> arch/x86/mm/fault.c:1094:62: warning: incorrect type in argument 4 (different base types)
> arch/x86/mm/fault.c:1094:62: expected unsigned int fault
> arch/x86/mm/fault.c:1094:62: got restricted vm_fault_t [usertype] fault
>
> This patch has fixed the warnings.
>
I'll be folding this into "mm: Create the new vm_fault_t type".
prev parent reply other threads:[~2019-01-09 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 18:37 [PATCH v2] x86/mm/fault.c: Convert to use vm_fault_t Souptick Joarder
2019-01-09 18:42 ` Andrew Morton [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=20190109104211.ce93b844df26c340100cfa14@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=x86@kernel.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 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).