From: Souptick Joarder <jrdr.linux@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dave.hansen@linux.intel.com, luto@kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
bp@alien8.de, "H. Peter Anvin" <hpa@zytor.com>,
X86 ML <x86@kernel.org>,
linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
ak@linux.intel.com
Subject: Re: [PATCH] x86/mm/fault.c: Convert to use vm_fault_t
Date: Wed, 9 Jan 2019 20:53:31 +0530 [thread overview]
Message-ID: <CAFqt6zbRA9AKvTy0riSFoUGNyqTVi_7WUPAkpySS1Sj28r+R5Q@mail.gmail.com> (raw)
In-Reply-To: <20190109152209.GA13599@jordon-HP-15-Notebook-PC>
On Wed, Jan 9, 2019 at 8:48 PM Souptick Joarder <jrdr.linux@gmail.com> wrote:
>
> Convert to use vm_fault_t type for last argument of do_sigbus().
>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
kbuild reported a warning during testing of final vm_fault_t patch integrated
in mm tree.
[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]
url: https://github.com/0day-ci/linux/commits/Souptick-Joarder/mm-Create-the-new-vm_fault_t-type/20190109-154216
This patch has fixed the warning.
> ---
> arch/x86/mm/fault.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
> index 2ff25ad..dea3725 100644
> --- a/arch/x86/mm/fault.c
> +++ b/arch/x86/mm/fault.c
> @@ -1031,7 +1031,7 @@ static inline bool bad_area_access_from_pkeys(unsigned long error_code,
>
> static void
> do_sigbus(struct pt_regs *regs, unsigned long error_code, unsigned long address,
> - unsigned int fault)
> + vm_fault_t fault)
> {
> struct task_struct *tsk = current;
>
> --
> 1.9.1
>
prev parent reply other threads:[~2019-01-09 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 15:22 [PATCH] x86/mm/fault.c: Convert to use vm_fault_t Souptick Joarder
2019-01-09 15:23 ` Souptick Joarder [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=CAFqt6zbRA9AKvTy0riSFoUGNyqTVi_7WUPAkpySS1Sj28r+R5Q@mail.gmail.com \
--to=jrdr.linux@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.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).