public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andy Shevchenko <andriy.shevchenko@linux•intel.com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: build failure after merge of the pinctrl-intel tree
Date: Thu, 20 Aug 2020 11:30:39 +1000	[thread overview]
Message-ID: <20200820113039.71120e6a@canb.auug.org.au> (raw)

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

Hi all,

After merging the pinctrl-intel tree, today's linux-next build (x86_64
allmodconfig) failed like this:

x86_64-linux-gnu-ld: drivers/pinctrl/intel/pinctrl-baytrail.o: in function `byt_pinctrl_probe':
pinctrl-baytrail.c:(.text+0x12bf): undefined reference to `intel_pinctrl_get_soc_data'

Caused by commit

  2db97df9f29d ("pinctrl: baytrail: Switch to use intel_pinctrl_get_soc_data()")

CONFIG_PINCTRL_BAYTRAIL=y
CONFIG_PINCTRL_INTEL=m

I have ised the pinctrl-intel tree from next-20200819 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-08-20  1:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  1:30 Stephen Rothwell [this message]
2020-08-20  9:40 ` linux-next: build failure after merge of the pinctrl-intel tree Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
2022-10-18  2:13 Stephen Rothwell
2022-10-18  2:20 ` Stephen Rothwell
2022-10-18 12:29 ` Andy Shevchenko
2026-05-07 10:47 Thierry Reding
2026-05-07 12:15 ` Thierry Reding
2026-05-11  6:09 ` Manikandan.M

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=20200820113039.71120e6a@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=andriy.shevchenko@linux$(echo .)intel.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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