Re: [PATCH, RFC 01/22] can: move CONFIG_HAVE_CAN_FLEXCAN out of CAN_DEV

2013-05-07 Thread Marc Kleine-Budde
On 05/03/2013 05:24 PM, Arnd Bergmann wrote: > On Friday 03 May 2013, Marc Kleine-Budde wrote: >> On 05/02/2013 05:16 PM, Arnd Bergmann wrote: >>> CONFIG_HAVE_CAN_FLEXCAN is a silect symbol that is meant to be selected >>> by platforms that support this driver, but that is not possible without >>>

Re: [PATCH, RFC 01/22] can: move CONFIG_HAVE_CAN_FLEXCAN out of CAN_DEV

2013-05-03 Thread Arnd Bergmann
On Friday 03 May 2013, Marc Kleine-Budde wrote: > On 05/02/2013 05:16 PM, Arnd Bergmann wrote: > > CONFIG_HAVE_CAN_FLEXCAN is a silect symbol that is meant to be selected > > by platforms that support this driver, but that is not possible without > > also selecting CAN_DEV, unless we move it out of

Re: [PATCH, RFC 01/22] can: move CONFIG_HAVE_CAN_FLEXCAN out of CAN_DEV

2013-05-03 Thread Marc Kleine-Budde
On 05/02/2013 05:16 PM, Arnd Bergmann wrote: > CONFIG_HAVE_CAN_FLEXCAN is a silect symbol that is meant to be selected > by platforms that support this driver, but that is not possible without > also selecting CAN_DEV, unless we move it out of the "if CAN_DEV" > section of the Kconfig file. > > wa

[PATCH, RFC 01/22] can: move CONFIG_HAVE_CAN_FLEXCAN out of CAN_DEV

2013-05-02 Thread Arnd Bergmann
CONFIG_HAVE_CAN_FLEXCAN is a silect symbol that is meant to be selected by platforms that support this driver, but that is not possible without also selecting CAN_DEV, unless we move it out of the "if CAN_DEV" section of the Kconfig file. warning: (SOC_IMX28 && SOC_IMX25 && SOC_IMX35 && IMX_HAVE_