linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-mm <linux-mm@kvack.org>,
	open list <linux-kernel@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [next] mm/nommu.c:1671:6: error: conflicting types for 'filemap_map_pages'
Date: Thu, 28 Jan 2021 16:26:09 +0100	[thread overview]
Message-ID: <CAMuHMdUzCFuuUcgMwh+numoCnr_p0tfTucybytymUceyPV0TBQ@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYta_uOLktmMnZHUTK9Uqx-rjtmQSSvHFCsvQsVdZDdm8A@mail.gmail.com>

Hi Naresh,

On Thu, Jan 28, 2021 at 3:25 PM Naresh Kamboju
<naresh.kamboju@linaro.org> wrote:
> arm, sh and riscv architecture build failed on today's Linux next tag 20210128.
>
> FYI,
> # CONFIG_MMU is not set on these failed configs.
> config file attached to this email.
>
> make --silent --keep-going --jobs=8 O=/home/tux  -
> build/.cache/tuxmake/builds/1/tmp ARCH=arm
> CROSS_COMPILE=arm-linux-gnueabihf- 'CC=sccache
> arm-linux-gnueabihf-gcc' 'HOSTCC=sccache gcc'
> mm/nommu.c:1671:6: error: conflicting types for 'filemap_map_pages'
>  1671 | void filemap_map_pages(struct vm_fault *vmf,
>       |      ^~~~~~~~~~~~~~~~~
> In file included from mm/nommu.c:20:
> include/linux/mm.h:2578:19: note: previous declaration of
> 'filemap_map_pages' was here
>  2578 | extern vm_fault_t filemap_map_pages(struct vm_fault *vmf,
>       |                   ^~~~~~~~~~~~~~~~~

Care to give "[PATCH -next] mm/nommu: Fix return type of
filemap_map_pages()" a try?
https://lore.kernel.org/lkml/20210128100626.2257638-1-geert@linux-m68k.org/

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-01-28 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 14:23 [next] mm/nommu.c:1671:6: error: conflicting types for 'filemap_map_pages' Naresh Kamboju
2021-01-28 15:26 ` Geert Uytterhoeven [this message]
2021-01-28 17:27   ` Naresh Kamboju
2021-01-28 18:09   ` Will Deacon

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=CAMuHMdUzCFuuUcgMwh+numoCnr_p0tfTucybytymUceyPV0TBQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=sfr@canb.auug.org.au \
    --cc=will@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).