From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.39
Date: Thu, 19 May 2011 17:16:32 +0100 [thread overview]
Message-ID: <BANLkTi=7v40xpM6-jQ2CS09fEb0noFLYPg@mail.gmail.com> (raw)
In-Reply-To: <4DD53AE5.8020103@teksavvy.com>
On 19 May 2011 16:44, Mark Lord <kernel@teksavvy.com> wrote:
> Here's some more funny business that was new after rc7-git12:
>
> warning: (AX88796_93CX6 && RTL8180 && RTL8187 && ADM8211 && RT2400PCI &&
> RT2500PCI && RT61PCI && RT2800PCI && R8187SE) selects EEPROM_93CX6 which has
> unmet direct dependencies (MISC_DEVICES)
> warning: (ACPI_APEI) selects PSTORE which has unmet direct dependencies
> (MISC_FILESYSTEMS)
>
> The exact same .config didn't do that with rc7-git12,
> but does do it with 2.6.39 final.
>
> Odd thing is, if I select both MISC_DEVICES and MISC_FILESYSTEMS,
> but do NOT select anything from under either of those,
> the warnings go away.
>
> Which likely means the warnings are totally bogus.
The problem is:
AX88796_93CX6 selects EEPROM_93CX6
EEPROM_93CX6 depends on MISC_DEVICES (as part of the EEPROM menu which
is only included if MISC_DEVICES)
By enabling MISC_DEVICES, you allow AX88796_93CX6 to select
EEPROM_93CX6 without any warning as it has the dependencies met.
The issue here is that EEPROM_93CX6 doesn't really depend on any
MISC_DEVICES infrastructure. That's just a directory for various
drivers and MISC_DEVICES only has a visibility role. There was a
proposal last year for kbuild to differentiate between dependency and
visibility but I don't know what happened to it.
--
Catalin
next prev parent reply other threads:[~2011-05-19 16:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 5:04 Linux 2.6.39 Linus Torvalds
2011-05-19 5:32 ` Stephen Rothwell
2011-05-19 15:26 ` Linux 2.6.39 -- *ERROR* Attempting to mmap a purgeable buffer Mark Lord
2011-05-20 22:00 ` Linus Torvalds
2011-05-21 1:57 ` Mark Lord
2011-05-19 15:44 ` Linux 2.6.39 Mark Lord
2011-05-19 15:47 ` Randy Dunlap
2011-05-19 16:16 ` Catalin Marinas [this message]
2011-05-19 16:23 ` Randy Dunlap
2011-05-23 10:49 ` Catalin Marinas
2011-05-21 17:56 ` Milan Oravec
2011-05-21 20:31 ` Ed Tomlinson
2011-05-23 22:08 ` Ed Tomlinson
2011-05-25 8:27 ` Ville Tervo
2011-05-25 21:19 ` Milan Oravec
2011-06-21 21:08 ` Milan Oravec
2011-05-22 1:12 ` Uwaysi Bin Kareem
2011-05-22 7:22 ` CaT
[not found] <BANLkTinG_qCtHQYRYFQUJ9oGv4H1cuznWg@mail.gmail.com>
2011-05-25 11:11 ` Ed Tomlinson
2011-05-25 11:36 ` Ville Tervo
2011-05-25 11:53 ` Corey Boyle
2011-05-25 12:12 ` Ed Tomlinson
2011-05-25 12:46 ` Cufi, Carles
2011-05-25 14:07 ` Corey Boyle
2011-05-25 14:15 ` Cufi, Carles
2011-05-25 16:31 ` Tom Allebrandi
2011-05-25 17:04 ` Cufi, Carles
2011-05-25 17:21 ` Tom Allebrandi
2011-05-26 1:11 ` Corey Boyle
2011-05-26 8:37 ` Ville Tervo
2011-05-26 10:17 ` Corey Boyle
2011-05-26 10:47 ` Ed Tomlinson
2011-05-30 21:02 ` Gustavo F. Padovan
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='BANLkTi=7v40xpM6-jQ2CS09fEb0noFLYPg@mail.gmail.com' \
--to=catalin.marinas@arm.com \
--cc=kernel@teksavvy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).