<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/scripts/kconfig/zconf.l, branch linux-2.6.23.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.23.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.23.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-05-06T07:27:15Z</updated>
<entry>
<title>kconfig: fix mconf segmentation fault</title>
<updated>2007-05-06T07:27:15Z</updated>
<author>
<name>Marcin Garski</name>
</author>
<published>2007-05-05T20:49:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=11de39e2fbbc592018e0a231d0ee773653dcc8d6'/>
<id>urn:sha1:11de39e2fbbc592018e0a231d0ee773653dcc8d6</id>
<content type='text'>
I have found small bug in mconf, when you run it without any argument it
will sigsegv.

Without patch:
$ scripts/kconfig/mconf
Segmentation fault

With patch:
$ scripts/kconfig/mconf
can't find file (null)

Signed-off-by: Marcin Garski &lt;mgarski@post.pl&gt;
Signed-off-by: Sam Ravnborg &lt;sam@ravnborg.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] kconfig: improve error handling in the parser</title>
<updated>2005-11-09T15:55:54Z</updated>
<author>
<name>Roman Zippel</name>
</author>
<published>2005-11-09T05:34:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a02f0570ae201c495ee991b959bb974af18f35cc'/>
<id>urn:sha1:a02f0570ae201c495ee991b959bb974af18f35cc</id>
<content type='text'>
Add a few error tokens to the parser to catch common errors and print more
descriptive error messages.

Signed-off-by: Roman Zippel &lt;zippel@linux-m68k.org&gt;
Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] kconfig: simplify symbol type parsing</title>
<updated>2005-11-09T15:55:54Z</updated>
<author>
<name>Roman Zippel</name>
</author>
<published>2005-11-09T05:34:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3370f9f0d9c7d14bf71aab27fa45c0537f130614'/>
<id>urn:sha1:3370f9f0d9c7d14bf71aab27fa45c0537f130614</id>
<content type='text'>
This simplifies the parser a bit by merging the various symbol types into a
single token and adds the type to the keyword hash.

Signed-off-by: Roman Zippel &lt;zippel@linux-m68k.org&gt;
Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] kconfig: use gperf for kconfig keywords</title>
<updated>2005-11-09T15:55:53Z</updated>
<author>
<name>Roman Zippel</name>
</author>
<published>2005-11-09T05:34:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7a88488bbc231e48a4a88ee2569bc0cc5d706f0a'/>
<id>urn:sha1:7a88488bbc231e48a4a88ee2569bc0cc5d706f0a</id>
<content type='text'>
Use gperf to generate a hash for the kconfig keywords.  This greatly reduces
the size of the generated scanner and makes it easier to extend kconfig.

Signed-off-by: Roman Zippel &lt;zippel@linux-m68k.org&gt;
Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>Linux-2.6.12-rc2</title>
<updated>2005-04-16T22:20:36Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2005-04-16T22:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2'/>
<id>urn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2</id>
<content type='text'>
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!
</content>
</entry>
</feed>
