From: Tejun Heo <tj@kernel.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Loc Ho <lho@apm.com>, Greg KH <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: [PATCH libata/for-3.15-fixes] libata: drop COMPILE_TEST from AHCI_XGENE
Date: Wed, 2 Apr 2014 12:36:45 -0400 [thread overview]
Message-ID: <20140402163645.GD16631@htj.dyndns.org> (raw)
In-Reply-To: <20140402162215.GC16631@htj.dyndns.org>
Hello, Kishon.
I'm converting AHCI_XGENE to depend on PHY_XGENE instead of selecting
it as dependency chaining through select doesn't work. Looking at the
PHY Kconfig options, I wonder whether we're going about this the right
way. Are PHY drivers meaningful at all w/o higher level drivers
making use of them? If not, why do we even have visible Kconfig opts
for them? Shouldn't we just chain everything through selects and
float the actual dependencies to the higher level drivers which the
users actually care about?
Thanks.
--
tejun
next prev parent reply other threads:[~2014-04-02 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 18:49 [GIT PULL] USB patches for 3.15-rc1 Greg KH
2014-04-02 0:28 ` Linus Torvalds
2014-04-02 2:28 ` Greg KH
2014-04-02 5:42 ` Loc Ho
2014-04-02 13:06 ` Kishon Vijay Abraham I
2014-04-02 14:45 ` Bartlomiej Zolnierkiewicz
2014-04-02 15:49 ` Loc Ho
2014-04-02 15:53 ` [PATCH libata/for-3.15-fixes] libata: drop COMPILE_TEST from AHCI_XGENE Tejun Heo
2014-04-02 15:58 ` Tejun Heo
2014-04-02 16:22 ` Tejun Heo
2014-04-02 16:36 ` Tejun Heo [this message]
2014-04-03 14:32 ` Bartlomiej Zolnierkiewicz
2014-04-03 14:49 ` Tejun Heo
2014-04-02 16:41 ` [PATCH libata/for-3.15-fixes] libata: make AHCI_XGENE depend on PHY_XGENE Tejun Heo
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=20140402163645.GD16631@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=lho@apm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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