linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: "kernel test robot" <lkp@intel.com>,
	"Álvaro Fernández Rojas" <noltari@gmail.com>,
	kbuild-all@lists.01.org,
	"Linux Memory Management List" <linux-mm@kvack.org>
Subject: Re: [linux-next:master 7287/10499] undefined reference to `pinconf_generic_dt_node_to_map'
Date: Thu, 8 Apr 2021 17:07:34 +0200	[thread overview]
Message-ID: <CACRpkdbVRdRR5tC-GE0NWyMJNAimfgPt7BpgTCrZmHMpHauvFQ@mail.gmail.com> (raw)
In-Reply-To: <CAOiHx=k8CWbZKPeO7N46ZjULQLz_g7WNJkXm_xTE6BqDVwmHZQ@mail.gmail.com>

On Thu, Apr 8, 2021 at 4:36 PM Jonas Gorski <jonas.gorski@gmail.com> wrote:
> On Thu, 8 Apr 2021 at 14:57, Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Thu, Apr 8, 2021 at 2:10 PM kernel test robot <lkp@intel.com> wrote:
> >
> > >    hppa-linux-ld: drivers/pinctrl/bcm/pinctrl-bcm63268.o: in function `pinconf_generic_dt_node_to_map_pin':
> > > >> (.text+0x174): undefined reference to `pinconf_generic_dt_node_to_map'
> >
> > Well that is interesting, as the Kconfig looks like this in the latest
> > -next tree:
> >
> > config PINCTRL_BCM63268
> >         bool "Broadcom BCM63268 GPIO driver"
> >         depends on (BMIPS_GENERIC || COMPILE_TEST)
> >         depends on OF
> >         select PINCTRL_BCM63XX
> >         default BMIPS_GENERIC
> >         help
> >            Say Y here to enable the Broadcom BCM63268 GPIO driver.
> >
> > depends on OF. But this config has:
> >   # CONFIG_OF is not set
> > So how is this happening?
>
> Not sure if this is a serious question, but if you check the robot
> output, it is explicitly building the commit that adds the driver (it
> even links the commit ;P), which is then obviously still missing the
> OF dependency fixes you and Randy added later.

Aha that explains it. No I didn't see the commit ID, I blame it
on information stress, when the robot sends me something I
assume it is building/testing HEAD.

I think the robot used to say something like "HEAD works, this only
hurts bisectability", that was helpful.

Yours,
Linus Walleij


      reply	other threads:[~2021-04-08 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 12:09 kernel test robot
2021-04-08 12:57 ` Linus Walleij
2021-04-08 14:36   ` Jonas Gorski
2021-04-08 15:07     ` Linus Walleij [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=CACRpkdbVRdRR5tC-GE0NWyMJNAimfgPt7BpgTCrZmHMpHauvFQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=jonas.gorski@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=noltari@gmail.com \
    /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