LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] macintosh/via-pmu: Fix build failure when CONFIG_INPUT is disabled
Date: Mon, 21 Mar 2022 19:29:11 +1100 (AEDT)	[thread overview]
Message-ID: <e8398356-8ba3-e9de-8da0-3591907340b5@linux-m68k.org> (raw)
In-Reply-To: <5291a177-9a67-b23a-515f-7faa3cc887e8@csgroup.eu>

[-- Attachment #1: Type: text/plain, Size: 2337 bytes --]

On Mon, 21 Mar 2022, Christophe Leroy wrote:

> 
> 
> Le 21/03/2022 à 05:30, Finn Thain a écrit :
> > drivers/macintosh/via-pmu-event.o: In function `via_pmu_event':
> > via-pmu-event.c:(.text+0x44): undefined reference to `input_event'
> > via-pmu-event.c:(.text+0x68): undefined reference to `input_event'
> > via-pmu-event.c:(.text+0x94): undefined reference to `input_event'
> > via-pmu-event.c:(.text+0xb8): undefined reference to `input_event'
> > drivers/macintosh/via-pmu-event.o: In function `via_pmu_event_init':
> > via-pmu-event.c:(.init.text+0x20): undefined reference to `input_allocate_device'
> > via-pmu-event.c:(.init.text+0xc4): undefined reference to `input_register_device'
> > via-pmu-event.c:(.init.text+0xd4): undefined reference to `input_free_device'
> > make[1]: *** [Makefile:1155: vmlinux] Error 1
> > make: *** [Makefile:350: __build_one_by_one] Error 2
> > 
> > Don't call into the input subsystem unless CONFIG_INPUT is built-in.
> > 
> > Reported-by: kernel test robot <lkp@intel.com>
> > Cc: Michael Ellerman <mpe@ellerman.id.au>
> > Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> > Cc: Randy Dunlap <rdunlap@infradead.org>
> > Signed-off-by: Finn Thain <fthain@linux-m68k.org>
> > ---
> > This is equivalent to the patch I sent a couple of days ago. This one
> > is slightly longer and adds a new symbol so that Kconfig logic can been
> > used instead of Makefile logic in case reviewers prefer that.
> > ---
> >   drivers/macintosh/Kconfig   | 5 +++++
> >   drivers/macintosh/Makefile  | 3 ++-
> >   drivers/macintosh/via-pmu.c | 2 ++
> >   3 files changed, 9 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/macintosh/Kconfig b/drivers/macintosh/Kconfig
> > index 5cdc361da37c..b9102f051bbb 100644
> > --- a/drivers/macintosh/Kconfig
> > +++ b/drivers/macintosh/Kconfig
> > @@ -67,6 +67,11 @@ config ADB_PMU
> >   	  this device; you should do so if your machine is one of those
> >   	  mentioned above.
> >   
> > +config ADB_PMU_EVENT
> > +	bool
> > +	depends on ADB_PMU && INPUT=y
> > +	default y
> 
> Could be reduced to
> 
> config ADB_PMU_EVENT
> 	def_bool y if ADB_PMU && INPUT=y
> 

That's great but my question remains unanswered: why the aversion to 
conditionals in Makefiles, when that would be simpler (no new symbol)?

  reply	other threads:[~2022-03-21  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21  4:30 [PATCH] macintosh/via-pmu: Fix build failure when CONFIG_INPUT is disabled Finn Thain
2022-03-21  6:37 ` Christophe Leroy
2022-03-21  8:29   ` Finn Thain [this message]
2022-03-21  8:47     ` Geert Uytterhoeven
2022-03-21  9:09       ` Finn Thain
  -- strict thread matches above, loose matches on Subject: below --
2022-03-19  4:18 Finn Thain
2022-03-19  4:56 ` Randy Dunlap
2022-03-19  5:57   ` Finn Thain
2022-03-19  9:24 ` Geert Uytterhoeven
2022-03-20  0:19   ` Finn Thain

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=e8398356-8ba3-e9de-8da0-3591907340b5@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rdunlap@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