All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Guenter Roeck <linux@roeck-us.net>,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Eddie James <eajames@linux.vnet.ibm.com>
Subject: linux-next: build failure after merge of the hwmon-staging tree
Date: Mon, 17 Dec 2018 10:00:26 +1100	[thread overview]
Message-ID: <20181217100026.03438bcf@canb.auug.org.au> (raw)

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

Hi Guenter,

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

drivers/hwmon/Kconfig:1298:warning: ignoring unsupported character '/'
drivers/hwmon/Kconfig:1299: syntax error
drivers/hwmon/Kconfig:1298:warning: ignoring unsupported character '/'
drivers/hwmon/Kconfig:1298:warning: ignoring unsupported character '/'
drivers/hwmon/Kconfig:1298: invalid statement

Caused by commit

  de75c2156b2f ("hwmon: Add On-Chip Controller (OCC) hwmon driver")

interacting with updates to the kconfig system.

I have applied the following merge fix patch for today.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 17 Dec 2018 09:50:14 +1100
Subject: [PATCH] hwmon: quote the path in Kconfig source statements

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/hwmon/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
index 62b68cd280dc..6f929bfa9fcd 100644
--- a/drivers/hwmon/Kconfig
+++ b/drivers/hwmon/Kconfig
@@ -1295,7 +1295,7 @@ config SENSORS_NSA320
 	  This driver can also be built as a module. If so, the module
 	  will be called nsa320-hwmon.
 
-source drivers/hwmon/occ/Kconfig
+source "drivers/hwmon/occ/Kconfig"
 
 config SENSORS_PCF8591
 	tristate "Philips PCF8591 ADC/DAC"
-- 
2.19.1

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2018-12-16 23:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 23:00 Stephen Rothwell [this message]
2019-02-25 23:55 linux-next: build failure after merge of the hwmon-staging tree Stephen Rothwell
2019-02-26  0:11 ` Guenter Roeck
2020-03-22 23:37 Stephen Rothwell
2020-03-22 23:45 ` Guenter Roeck
2020-04-28  6:36 Stephen Rothwell
2020-04-28 13:19 ` Guenter Roeck
2020-08-24  0:28 Stephen Rothwell
2020-08-24  7:01 ` Guenter Roeck
2020-10-01  2:53 Stephen Rothwell
2020-10-01 15:09 ` Guenter Roeck
2022-05-10 12:26 Stephen Rothwell
2022-08-30 23:30 Stephen Rothwell
2022-08-31 12:03 ` Michael Shych
2023-01-24 22:24 Stephen Rothwell
2023-01-24 22:27 ` Guenter Roeck
2023-07-27  5:41 Stephen Rothwell

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=20181217100026.03438bcf@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=eajames@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=yamada.masahiro@socionext.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 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.