From: Paul Cercueil <paul@crapouillou.net>
To: Bin Liu <b-liu@ti.com>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [v2,3/4] usb: musb: Kconfig: Drop dependency on MACH_JZ4740 for jz4740
Date: Thu, 17 Jan 2019 19:31:27 -0300 [thread overview]
Message-ID: <1547764287.2057.0@crapouillou.net> (raw)
Hi,
On Tue, Jan 15, 2019 at 1:26 PM, Bin Liu <b-liu@ti.com> wrote:
> Hi Paul,
>
> On Thu, Jan 10, 2019 at 10:36:59AM -0300, Paul Cercueil wrote:
>> Depending on MACH_INGENIC prevent us from creating a generic kernel
>> that
>
> Again, did you mean MACH_JZ4740 instead?
Dammit. I'm sorry. Will send a v3 right now.
>> works on more than one MIPS board. Instead, we just depend on MIPS
>> being
>> set.
>>
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net
>> <mailto:paul@crapouillou.net>>
>> ---
>>
>> v2: Remove info about adding COMPILE_TEST in commit message, as it
>> was
>> there before
>>
>> drivers/usb/musb/Kconfig | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
>> index ad08895e78f9..6f5b0ed6a507 100644
>> --- a/drivers/usb/musb/Kconfig
>> +++ b/drivers/usb/musb/Kconfig
>> @@ -111,7 +111,7 @@ config USB_MUSB_UX500
>> config USB_MUSB_JZ4740
>> tristate "JZ4740"
>> depends on NOP_USB_XCEIV
>> - depends on MACH_JZ4740 || COMPILE_TEST
>> + depends on MIPS || COMPILE_TEST
>> depends on USB_MUSB_GADGET
>> depends on USB_OTG_BLACKLIST_HUB
>
> Regards,
> -Bin.
next reply other threads:[~2019-01-17 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 22:31 Paul Cercueil [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-15 16:26 [v2,3/4] usb: musb: Kconfig: Drop dependency on MACH_JZ4740 for jz4740 Bin Liu
2019-01-10 13:36 Paul Cercueil
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=1547764287.2057.0@crapouillou.net \
--to=paul@crapouillou.net \
--cc=b-liu@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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