From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sebastian Reichel <sre@kernel.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>
Subject: Re: linux-next: build warning after merge of the battery tree
Date: Thu, 25 Sep 2014 09:00:34 +0200 [thread overview]
Message-ID: <1411628434.16755.3.camel@AMDC1943> (raw)
In-Reply-To: <20140925142206.5ebea1eb@canb.auug.org.au>
On czw, 2014-09-25 at 14:22 +1000, Stephen Rothwell wrote:
> Hi Sebastian,
>
> After merging the battery tree, today's linux-next build (powerpc
> ppc64_defconfig and x86_64 allmodconfig) produced this warning:
>
> fs/sysfs/Kconfig:1:error: recursive dependency detected!
> fs/sysfs/Kconfig:1: symbol SYSFS is selected by CHARGER_MAX14577
> drivers/power/Kconfig:327: symbol CHARGER_MAX14577 depends on POWER_SUPPLY
> drivers/power/Kconfig:1: symbol POWER_SUPPLY is selected by HID_SONY
> drivers/hid/Kconfig:649: symbol HID_SONY depends on NEW_LEDS
> drivers/leds/Kconfig:8: symbol NEW_LEDS is selected by SENSORS_APPLESMC
> drivers/hwmon/Kconfig:299: symbol SENSORS_APPLESMC depends on HWMON
> drivers/hwmon/Kconfig:5: symbol HWMON is selected by EEEPC_LAPTOP
> drivers/platform/x86/Kconfig:496: symbol EEEPC_LAPTOP depends on HOTPLUG_PCI
> drivers/pci/hotplug/Kconfig:5: symbol HOTPLUG_PCI depends on SYSFS
>
> Caused by commit e30110e9c96f ("charger: max14577: Configure
> battery-dependent settings from DTS and sysfs"). Consider depending on
> SYSFS instead of selecting it ... or maybe making your driver work even
> without it.
I'll send a patch changing to "depends on".
Best regards,
Krzysztof
next prev parent reply other threads:[~2014-09-25 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 4:22 linux-next: build warning after merge of the battery tree Stephen Rothwell
2014-09-25 7:00 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-05 1:53 Stephen Rothwell
2017-01-05 23:29 ` Sebastian Reichel
2012-06-19 4:54 Stephen Rothwell
2012-06-19 5:02 ` Anton Vorontsov
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=1411628434.16755.3.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sre@kernel.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;
as well as URLs for NNTP newsgroup(s).