linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-um <linux-um@lists.infradead.org>
Subject: Re: Build regressions/improvements in v5.8-rc6
Date: Mon, 20 Jul 2020 19:20:40 +0200	[thread overview]
Message-ID: <2b2e1695f6d9341f357f12ffdce59c06e36a383b.camel@sipsolutions.net> (raw)
In-Reply-To: <CAMuHMdUB5kFC5R6b6-OxPfP-PRLYBOK_d7dPjU_LcmYuLtGJpg@mail.gmail.com>

On Mon, 2020-07-20 at 16:01 +0200, Geert Uytterhoeven wrote:
> On Mon, Jul 20, 2020 at 3:12 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > JFYI, when comparing v5.8-rc6[1] to v5.8-rc5[3], the summaries are:
> >   - build errors: +6/-3
> 
>   + error: modpost: "devm_ioremap"
> [drivers/net/ethernet/xilinx/ll_temac.ko] undefined!:  => N/A
>   + error: modpost: "devm_ioremap_resource"
> [drivers/net/ethernet/xilinx/xilinx_emac.ko] undefined!:  => N/A
>   + error: modpost: "devm_of_iomap"
> [drivers/net/ethernet/xilinx/ll_temac.ko] undefined!:  => N/A
>   + error: modpost: "devm_platform_ioremap_resource"
> [drivers/iio/adc/adi-axi-adc.ko] undefined!:  => N/A
>   + error: modpost: "devm_platform_ioremap_resource"
> [drivers/ptp/ptp_ines.ko] undefined!:  => N/A
>   + error: modpost: "devm_platform_ioremap_resource"
> [drivers/staging/clocking-wizard/clk-xlnx-clock-wizard.ko] undefined!:
>  => N/A
> 
> um-x86_64/um-all{mod,yes}config

Must be an issue with those drivers - ARCH=um can't do ioremap(). The
drivers should depend on HAS_IOMEM or something like that?

johannes


      reply	other threads:[~2020-07-20 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 13:07 Build regressions/improvements in v5.8-rc6 Geert Uytterhoeven
2020-07-20 14:01 ` Geert Uytterhoeven
2020-07-20 17:20   ` Johannes Berg [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=2b2e1695f6d9341f357f12ffdce59c06e36a383b.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.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).