From: Greg KH <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Dave Penkler <dpenkler@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
sfr@canb.auug.org.au
Subject: Re: [PATCH] staging: gpib: Workaround for ppc build failure
Date: Mon, 16 Dec 2024 08:58:44 +0100 [thread overview]
Message-ID: <2024121622-sensitive-curtain-7d45@gregkh> (raw)
In-Reply-To: <b6102c6b-693f-4237-8c0c-83c5936aab3c@roeck-us.net>
On Sun, Dec 15, 2024 at 03:23:55PM -0800, Guenter Roeck wrote:
> On Wed, Dec 04, 2024 at 02:47:36PM +0100, Dave Penkler wrote:
> > Make GPIB_FMH depend on !PPC
> >
> > Reported_by: Stephen Rothwell <sfr@canb.auug.org.au>
> > Link: https://lore.kernel.org/all/20241015165538.634707e5@canb.auug.org.au/
> >
> > Signed-off-by: Dave Penkler <dpenkler@gmail.com>
>
> This patch just exposes other build failures, for example
> i386:allyesconfig or x86_64:allyesconfig.
>
> Error log:
> x86_64-linux-ld: vmlinux.o: in function `fmh_gpib_t1_delay':
> fmh_gpib.c:(.text+0xfd49dbd): undefined reference to `nec7210_t1_delay'
>
> There are many more missing functions. FWIW, I don't know how this is
> supposed to work in the first place, since pretty much all gpib Makefiles
> say
>
> obj-m += <object file>
>
> meaning they won't be built with allyesconfig. fmh_gpib is the only
> exception with
>
> obj-$(CONFIG_GPIB_FMH) += fmh_gpib.o
>
> which means it _will_ be built with allyesconfig. So it is not surprising
> that it fails to link allyesconfig builds. Actually, it will fail all builds
> with CONFIG_GPIB_FMH=y.
Arnd has a patch for this that I'll be queueing up this week and getting
to Linus also this week.
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-16 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 13:47 [PATCH] staging: gpib: Workaround for ppc build failure Dave Penkler
2024-12-15 23:23 ` Guenter Roeck
2024-12-16 7:58 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 22:24 kernel test robot
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=2024121622-sensitive-curtain-7d45@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.