public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* bloated defconfigs
@ 2018-07-28 12:59 Andreas Kemnade
  2018-07-28 13:01 ` Andy Shevchenko
  0 siblings, 1 reply; 3+ messages in thread
From: Andreas Kemnade @ 2018-07-28 12:59 UTC (permalink / raw)
  To: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

Hi,

I just stumbled upon our defconfigs.

andi@aktux:~/gta04/gta04-kernel$ ls -l arch/arm/configs/ -Sr | tail -n
10 -rw-r--r-- 1 andi andi   9524 Apr  7 14:53 imote2_defconfig
-rw-r--r-- 1 andi andi   9985 Jul 28 13:34 imx_v6_v7_defconfig
-rw-r--r-- 1 andi andi  10118 Apr  7 14:53 ezx_defconfig
-rw-r--r-- 1 andi andi  10665 Apr  7 14:53 s3c2410_defconfig
-rw-r--r-- 1 andi andi  13161 May 29 18:14 omap2plus_defconfig
-rw-r--r-- 1 andi andi  17834 May 29 18:14 pxa_defconfig
-rw-r--r-- 1 andi andi  24624 Jul 28 13:34 multi_v7_defconfig
-rw-r--r-- 1 andi andi 157222 Jul 28 13:34 letux_udoo_defconfig
-rw-r--r-- 1 andi andi 157271 Jul 28 13:34 letux_lpae_defconfig
-rw-r--r-- 1 andi andi 157352 Jul 28 13:34 letux_defconfig


So we are bloated somehow. So I am wondering how these defconfigs are created.
AFAIK the tool is

make ARCH=arm CROSS_COMPILE=... savedefconfig

the file can then be used as a defconfig. I just did it and copied it over to
.config and used
make ARCH=arm CROSS_COMPILE=... olddefconfig

The result is the same. But the defconfig created by savedefconfig is only 20KB.
Well, what is the advantage? We have a better overview where we have
non-default values.

Regards,
Andreas

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bloated defconfigs
  2018-07-28 12:59 bloated defconfigs Andreas Kemnade
@ 2018-07-28 13:01 ` Andy Shevchenko
  2018-07-28 13:03   ` Andreas Kemnade
  0 siblings, 1 reply; 3+ messages in thread
From: Andy Shevchenko @ 2018-07-28 13:01 UTC (permalink / raw)
  To: Andreas Kemnade; +Cc: Linux Kernel Mailing List

On Sat, Jul 28, 2018 at 3:59 PM, Andreas Kemnade <andreas@kemnade.info> wrote:
> Hi,
>
> I just stumbled upon our defconfigs.
>
> andi@aktux:~/gta04/gta04-kernel$ ls -l arch/arm/configs/ -Sr | tail -n
> 10 -rw-r--r-- 1 andi andi   9524 Apr  7 14:53 imote2_defconfig
> -rw-r--r-- 1 andi andi   9985 Jul 28 13:34 imx_v6_v7_defconfig
> -rw-r--r-- 1 andi andi  10118 Apr  7 14:53 ezx_defconfig
> -rw-r--r-- 1 andi andi  10665 Apr  7 14:53 s3c2410_defconfig
> -rw-r--r-- 1 andi andi  13161 May 29 18:14 omap2plus_defconfig
> -rw-r--r-- 1 andi andi  17834 May 29 18:14 pxa_defconfig
> -rw-r--r-- 1 andi andi  24624 Jul 28 13:34 multi_v7_defconfig
> -rw-r--r-- 1 andi andi 157222 Jul 28 13:34 letux_udoo_defconfig
> -rw-r--r-- 1 andi andi 157271 Jul 28 13:34 letux_lpae_defconfig
> -rw-r--r-- 1 andi andi 157352 Jul 28 13:34 letux_defconfig
>
>
> So we are bloated somehow. So I am wondering how these defconfigs are created.
> AFAIK the tool is
>
> make ARCH=arm CROSS_COMPILE=... savedefconfig
>
> the file can then be used as a defconfig. I just did it and copied it over to
> .config and used
> make ARCH=arm CROSS_COMPILE=... olddefconfig
>
> The result is the same. But the defconfig created by savedefconfig is only 20KB.
> Well, what is the advantage? We have a better overview where we have
> non-default values.

So, why not to send patches?


-- 
With Best Regards,
Andy Shevchenko

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bloated defconfigs
  2018-07-28 13:01 ` Andy Shevchenko
@ 2018-07-28 13:03   ` Andreas Kemnade
  0 siblings, 0 replies; 3+ messages in thread
From: Andreas Kemnade @ 2018-07-28 13:03 UTC (permalink / raw)
  To: Andy Shevchenko; +Cc: Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]

Hi,

On Sat, 28 Jul 2018 16:01:41 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Sat, Jul 28, 2018 at 3:59 PM, Andreas Kemnade <andreas@kemnade.info> wrote:
> > Hi,
> >
> > I just stumbled upon our defconfigs.
> >
> > andi@aktux:~/gta04/gta04-kernel$ ls -l arch/arm/configs/ -Sr | tail -n
> > 10 -rw-r--r-- 1 andi andi   9524 Apr  7 14:53 imote2_defconfig
> > -rw-r--r-- 1 andi andi   9985 Jul 28 13:34 imx_v6_v7_defconfig
> > -rw-r--r-- 1 andi andi  10118 Apr  7 14:53 ezx_defconfig
> > -rw-r--r-- 1 andi andi  10665 Apr  7 14:53 s3c2410_defconfig
> > -rw-r--r-- 1 andi andi  13161 May 29 18:14 omap2plus_defconfig
> > -rw-r--r-- 1 andi andi  17834 May 29 18:14 pxa_defconfig
> > -rw-r--r-- 1 andi andi  24624 Jul 28 13:34 multi_v7_defconfig
> > -rw-r--r-- 1 andi andi 157222 Jul 28 13:34 letux_udoo_defconfig
> > -rw-r--r-- 1 andi andi 157271 Jul 28 13:34 letux_lpae_defconfig
> > -rw-r--r-- 1 andi andi 157352 Jul 28 13:34 letux_defconfig
> >
> >
> > So we are bloated somehow. So I am wondering how these defconfigs are created.
> > AFAIK the tool is
> >
> > make ARCH=arm CROSS_COMPILE=... savedefconfig
> >
> > the file can then be used as a defconfig. I just did it and copied it over to
> > .config and used
> > make ARCH=arm CROSS_COMPILE=... olddefconfig
> >
> > The result is the same. But the defconfig created by savedefconfig is only 20KB.
> > Well, what is the advantage? We have a better overview where we have
> > non-default values.  
> 
> So, why not to send patches?
> 
sorry for the noise, wrong list, these bloated letux*defconfigs are not
mainline.

Regards,
Andreas

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-07-28 13:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-07-28 12:59 bloated defconfigs Andreas Kemnade
2018-07-28 13:01 ` Andy Shevchenko
2018-07-28 13:03   ` Andreas Kemnade

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox