linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Subject: Re: [linux-next:master 4620/4884] kernel/irq/generic-chip.c:210:9: error: call to undeclared function 'ioread32be'; ISO C99 and later do not support implicit function declarations
Date: Tue, 05 Dec 2023 13:42:12 +0100	[thread overview]
Message-ID: <7bdbb86a-ccf8-4a71-b25f-52a98ebf2d67@app.fastmail.com> (raw)
In-Reply-To: <202312051917.ldwRetjX-lkp@intel.com>

On Tue, Dec 5, 2023, at 12:36, kernel test robot wrote:
> tree:   
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 
> master
> head:   0f5f12ac05f36f117e793656c3f560625e927f1b
> commit: 17229c19e5bf0b5dc8b68dc4ca4e7012e7da4747 [4620/4884] mips: 
> remove extraneous asm-generic/iomap.h include

> If you fix the issue in a separate patch/commit (i.e. not just a new 
> version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: 
> https://lore.kernel.org/oe-kbuild-all/202312051917.ldwRetjX-lkp@intel.com/
>
> Note: the linux-next/master HEAD 
> 0f5f12ac05f36f117e793656c3f560625e927f1b builds fine.
>       It may have been fixed somewhere.
>
> All error/warnings (new ones prefixed by >>):
>
>>> kernel/irq/generic-chip.c:210:9: error: call to undeclared function 'ioread32be'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>      210 |         return ioread32be(addr);
>          |                ^

This patch depends on the asm-generic/io.h cleanup series by
Jiaxun Yang and Baoquan He, which I have in my asm-generic
tree.

I've added my patch on top now, as it fits the general idea,
so this can be dropped from -mm (and not merged into the mips
tree).

     Arnd


      reply	other threads:[~2023-12-05 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 11:36 kernel test robot
2023-12-05 12:42 ` Arnd Bergmann [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=7bdbb86a-ccf8-4a71-b25f-52a98ebf2d67@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tsbogend@alpha.franken.de \
    /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