[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5ca19952e55e4a719ecd7034ca595aba@BY2PR03MB505.namprd03.prod.outlook.com>
Date: Thu, 20 Feb 2014 08:44:52 +0000
From: "Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>
To: Mark Brown <broonie@...nel.org>
CC: "lgirdwood@...il.com" <lgirdwood@...il.com>,
"guangyu.chen@...escale.com" <guangyu.chen@...escale.com>,
"shawn.guo@...aro.org" <shawn.guo@...aro.org>,
"perex@...ex.cz" <perex@...ex.cz>, "tiwai@...e.de" <tiwai@...e.de>,
"Fabio.Estevam@...escale.com" <Fabio.Estevam@...escale.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/2] ASoC: fsl: Make Freescale SAI/ESAI/SPDIF to be
visible in Kconfig
> Subject: Re: [PATCH 2/2] ASoC: fsl: Make Freescale SAI/ESAI/SPDIF to be
> visible in Kconfig
>
> On Thu, Feb 20, 2014 at 02:06:20AM +0000, Li.Xiubo@...escale.com wrote:
>
> > I'm not very sure of this patch, maybe should we add one menu
> > in Kconfig for all visible CPU DAIs firstly like for code drivers?
>
> Allowing them to be individually selected is definitely useful if people
> are trying to minimise their kernel size and/or build time. However
> none of the other Freescale people have commented on this patch (which
> I'd have expected) so I was giving them time and IIRC it needs a rebase
> against current code.
Yes, Surely.
As we can see that there will be many CPU DAI drivers to be visible in the
future, and they will get a bit noisy too. IMHO, put the CPU DAI drivers in
a menu is a good choice for other separate patches.
Thanks very much,
--
Best Regards,
Xiubo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists