[PATCH 1/4] usb: chipidea: improve kconfig 2.0

2013-07-31 Thread Lothar Waßmann
This patch provides a cleaner solution to the problem described in commit 20a677fd. The goal to be achieved is to force USB_CHIPIDEA=m if either USB_EHCI_HCD=m or USB_GADGET=m. If both are 'y' USB_CHIPIDEA may be selected to be 'm' or 'y'. The old patch had the drawback, that USB_CHIPIDEA could b

Re: [PATCH 1/4] usb: chipidea: improve kconfig 2.0

2013-08-09 Thread Alexander Shishkin
Lothar Waßmann writes: > This patch provides a cleaner solution to the problem described in > commit 20a677fd. > > The goal to be achieved is to force USB_CHIPIDEA=m if either > USB_EHCI_HCD=m or USB_GADGET=m. > If both are 'y' USB_CHIPIDEA may be selected to be 'm' or 'y'. > > The old patch had

Re: [PATCH 1/4] usb: chipidea: improve kconfig 2.0

2013-07-31 Thread Sergei Shtylyov
Hello. On 07/31/2013 06:21 PM, Lothar Waßmann wrote: This patch provides a cleaner solution to the problem described in commit 20a677fd. Please also specify that commit's summary line in parens. The goal to be achieved is to force USB_CHIPIDEA=m if either USB_EHCI_HCD=m or USB_GADGET=m.

Re: [PATCH 1/4] usb: chipidea: improve kconfig 2.0

2013-07-31 Thread Peter Chen
On Wed, Jul 31, 2013 at 04:21:13PM +0200, Lothar Waßmann wrote: > This patch provides a cleaner solution to the problem described in > commit 20a677fd. > > The goal to be achieved is to force USB_CHIPIDEA=m if either > USB_EHCI_HCD=m or USB_GADGET=m. > If both are 'y' USB_CHIPIDEA may be selected