From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: onfig: multi_v7: Update it for Keystone defconfig
Date: Mon, 29 Dec 2014 10:43:50 -0800 [thread overview]
Message-ID: <54A1A0E6.9000504@oracle.com> (raw)
In-Reply-To: <20141229172034.GK29379@saruman>
On 12/29/2014 9:20 AM, Felipe Balbi wrote:
> Hi,
>
> subject typo: s/onfig/config/
>
> On Mon, Dec 29, 2014 at 09:13:27AM -0800, Santosh Shilimkar wrote:
>> @@ -346,9 +354,13 @@ CONFIG_USB_OHCI_HCD=y
>> CONFIG_USB_OHCI_HCD_STI=y
>> CONFIG_USB_OHCI_HCD_PLATFORM=y
>> CONFIG_USB_STORAGE=y
>> +CONFIG_USB_DWC3=y
>> +CONFIG_USB_DWC3_DEBUG=y
>> +CONFIG_USB_DWC3_VERBOSE=y
>
> you don't really need DEBUG or VERBOSE to be enabled always.
>
Right. Will fix that
prev parent reply other threads:[~2014-12-29 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 17:13 [PATCH] ARM: onfig: multi_v7: Update it for Keystone defconfig Santosh Shilimkar
2014-12-29 17:20 ` Felipe Balbi
2014-12-29 18:43 ` santosh shilimkar [this message]
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=54A1A0E6.9000504@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=linux-arm-kernel@lists.infradead.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).