From: "Arend van Spriel" <arend@broadcom.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Felipe Balbi <balbi@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: OMAP build failure after this merge window - caused by usb or phy Kconfig krap
Date: Mon, 25 Nov 2013 18:50:38 +0100 [thread overview]
Message-ID: <52938DEE.4030905@broadcom.com> (raw)
In-Reply-To: <20131125140927.GP16735@n2100.arm.linux.org.uk>
On 11/25/2013 03:09 PM, Russell King - ARM Linux wrote:
> which just illustrates why "select" in Kconfig is soo fscking bad that
> it shouldn't be used.
The problem is that instinctively people assume that select is the
opposite from depends. Unfortunately, it is not and it is a pitfall for
many.
Gr. AvS
WARNING: multiple messages have this Message-ID (diff)
From: arend@broadcom.com (Arend van Spriel)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP build failure after this merge window - caused by usb or phy Kconfig krap
Date: Mon, 25 Nov 2013 18:50:38 +0100 [thread overview]
Message-ID: <52938DEE.4030905@broadcom.com> (raw)
In-Reply-To: <20131125140927.GP16735@n2100.arm.linux.org.uk>
On 11/25/2013 03:09 PM, Russell King - ARM Linux wrote:
> which just illustrates why "select" in Kconfig is soo fscking bad that
> it shouldn't be used.
The problem is that instinctively people assume that select is the
opposite from depends. Unfortunately, it is not and it is a pitfall for
many.
Gr. AvS
next prev parent reply other threads:[~2013-11-25 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 14:09 OMAP build failure after this merge window - caused by usb or phy Kconfig krap Russell King - ARM Linux
2013-11-25 14:09 ` Russell King - ARM Linux
2013-11-25 17:50 ` Arend van Spriel [this message]
2013-11-25 17:50 ` Arend van Spriel
2013-11-25 17:55 ` Felipe Balbi
2013-11-25 17:55 ` Felipe Balbi
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=52938DEE.4030905@broadcom.com \
--to=arend@broadcom.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.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.