> Does the linux-tiny approach of adding a kconfig variable for
> each 5kB of code actually make sense? I'm asking since an
> exploding amount of kconfig variables and their
> interdependencies have a not so small maintainance impact in
> the long term.
I don't want to answer for the general case,
Nice.
Would it be helpful to compare .config.old to .config if you
don't provide any command line arguments?
scripts/diffconfig
would then do the job.
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to [EMAIL PROTECTED]
More majordomo info a
> Linux-embedded is the place to be, folks.
Another thing that I just noticed: According to
http://vger.kernel.org/vger-lists.html#linux-embedded
there is no mailing list archive for this list.
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message
> Linux-embedded is the place to be, folks.
This is the first time I've heard about linux-embedded.
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Maybe change the Kconfig entry so that:
* with CONFIG_EMBEDDED=y it's configuration
* with CONFIG_EMBEDDED=n it's on by default
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/
