Hi,
On Mon, 21 May 2007, Sam Ravnborg wrote:
> > A simple example would be
> > help texts, right now they are per symbol, but they should really be per
> > menu, so archs can provide different help texts for something.
>
> This one turned out easy.
> I assume what you had in mind was
Hi,
On Mon, 21 May 2007, Sam Ravnborg wrote:
A simple example would be
help texts, right now they are per symbol, but they should really be per
menu, so archs can provide different help texts for something.
This one turned out easy.
I assume what you had in mind was something like
> A simple example would be
> help texts, right now they are per symbol, but they should really be per
> menu, so archs can provide different help texts for something.
This one turned out easy.
I assume what you had in mind was something like the attached.
With this the help entry present is
On Mon, May 21, 2007 at 03:43:45AM +0200, Roman Zippel wrote:
> Hi,
>
> On Sun, 20 May 2007, Sam Ravnborg wrote:
>
> > I did a quick hack so kconfig could scan all Kconfig files
> > in the kernel tree.
> > By scanning all Kconfig files we gain the following:
> >
> > -> kconfig can report when a
On Mon, May 21, 2007 at 03:43:45AM +0200, Roman Zippel wrote:
Hi,
On Sun, 20 May 2007, Sam Ravnborg wrote:
I did a quick hack so kconfig could scan all Kconfig files
in the kernel tree.
By scanning all Kconfig files we gain the following:
- kconfig can report when a depends on
A simple example would be
help texts, right now they are per symbol, but they should really be per
menu, so archs can provide different help texts for something.
This one turned out easy.
I assume what you had in mind was something like the attached.
With this the help entry present is no
On Mon, 21 May 2007 03:43:45 +0200 (CEST) Roman Zippel wrote:
> Hi,
>
> On Sun, 20 May 2007, Sam Ravnborg wrote:
>
> > I did a quick hack so kconfig could scan all Kconfig files
> > in the kernel tree.
> > By scanning all Kconfig files we gain the following:
> >
> > -> kconfig can report when
Hi,
On Sun, 20 May 2007, Sam Ravnborg wrote:
> I did a quick hack so kconfig could scan all Kconfig files
> in the kernel tree.
> By scanning all Kconfig files we gain the following:
>
> -> kconfig can report when a depends on refer to an undefined symbol
> -> kconfig can report when a select
I did a quick hack so kconfig could scan all Kconfig files
in the kernel tree.
By scanning all Kconfig files we gain the following:
-> kconfig can report when a depends on refer to an undefined symbol
-> kconfig can report when a select refer to an undefined symbol
Later we can push a lot of
I did a quick hack so kconfig could scan all Kconfig files
in the kernel tree.
By scanning all Kconfig files we gain the following:
- kconfig can report when a depends on refer to an undefined symbol
- kconfig can report when a select refer to an undefined symbol
Later we can push a lot of
Hi,
On Sun, 20 May 2007, Sam Ravnborg wrote:
I did a quick hack so kconfig could scan all Kconfig files
in the kernel tree.
By scanning all Kconfig files we gain the following:
- kconfig can report when a depends on refer to an undefined symbol
- kconfig can report when a select refer to
On Mon, 21 May 2007 03:43:45 +0200 (CEST) Roman Zippel wrote:
Hi,
On Sun, 20 May 2007, Sam Ravnborg wrote:
I did a quick hack so kconfig could scan all Kconfig files
in the kernel tree.
By scanning all Kconfig files we gain the following:
- kconfig can report when a depends on
12 matches
Mail list logo
