On Mon, 2010-07-19 at 16:37 +0200, ext Arjan van de Ven wrote:
> On 7/19/2010 7:35 AM, Ameya Palande wrote:
> > Hi Arjan,
> >
> > On Mon, 2010-07-19 at 16:16 +0200, ext Arjan van de Ven wrote:
> >
> >> On 7/19/2010 7:10 AM, Ameya Palande wrote:
> >>
> >>> Hi,
> >>>
> >>> Today while cleaning config-arm* I found out following option (there
> >>> might be more) in config-generic:
> >>>
> >>> CONFIG_EEPROM_93CX6=m
> >>>
> >>> It should be moved to config-x86-generic or
> >>> config-x86-{mrst,netbook,ivi} where ever appropriate. Right now it is
> >>> flowing into config-arm* which is not correct.
> >>>
> >>>
> >> what is the exact problem you have? you're not saying what the problem
> >> is with this....
> >>
> > I guess I made it clear from above sentence: "Right now it is
> > flowing into config-arm* which is not correct."
> >
> > We don't want CONFIG_EEPROM_93CX6 to be set as "m" in any of the arm
> > configs at this point. And it is being set as "m" in config-arm-n900
> > which is not correct.
> >
>
> maybe I was not clear, haven't had coffee yet this morning... but what
> is the problem with it being m ?
> why is having a module "not correct"? Even if you don't use the guy,
> it's a module.... just don't use it.
Disadvantages:
1. Occupies space in root file system
2. Consumes resources on build server while building
3. ARM kernel rpm size is unnecessarily increased
IMO keeping things separate is better like config-arm-generic and
config-x86-generic which is currently non existent.
Cheers,
Ameya.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
