1/3 definitions of CONFIG_MODVERSIONS have trivially different banners.

1/11 definitions of CONFIG_HOTPLUG have trivially different banners.

2/10 definitions of CONFIG_CD_NO_IDESCSI have trivially different banners.

1/3 definitions of 64-bit CONFIG_BINFMT_ELF have trivially different banners.
1/3 definitions of CONFIG_BINFMT_ELF32 have trivially different banners.

1/17 definitions of CONFIG_SCSI have trivially different banners.

1/14 definitions of CONFIG_SOUND have trivially different banners.

2/4 definitions of CONFIG_SOFT_WATCHDOG have trivially different banners.

1/3 definitions of CONFIG_PSMOUSE have trivially different banners.

1/3 definitions of CONFIG_PPP have trivially different banners.

2/6 definitions of CONFIG_PCI have trivially different banners.

2/5 definitions of CONFIG_BLK_DEV_SR have trivially different banners.

1/5 definitions of CONFIG_PREEMPT have trivially different banners.

Symbol CONFIG_SK_G16 depends on CONFIG_OBSOLETE but does
not say so in its banner.

Symbol CONFIG_H8 depends on CONFIG_OBSOLETE but does
not say so in its banner.

Symbol CONFIG_FMV18X depends on CONFIG_OBSOLETE but does
not say so in its banner.

Symbol CONFIG_LDM_PARTITION depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Symbol CONFIG_JFFS2_FS_NAND depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Symbol CONFIG_ISDN_DRV_TPAM depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Three symbols CONFIG_BLK_DEV_ATARAID, CONFIG_BLK_DEV_ATARAID_PDC, and
CONFIG_BLK_DEV_ATARAID_HPT depend on CONFIG_EXPERIMENTAL but do
not say so in their banners.

Two symbols CONFIG_PLX_HERMES and CONFIG_PCI_HERMES depend on
CONFIG_EXPERIMENTAL but do not say so in their banners.

Symbol CONFIG_CYCLOMX_X25 depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Symbol CONFIG_BLK_DEV_UMEM depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Four symbols CONFIG_ATM_CLIP, CONFIG_ATM_CLIP_NO_ICMP, CONFIG_ATM_LANE,
and CONFIG_ATM_MPOA depend on CONFIG_EXPERIMENTAL but do not say so
in their banners.

Symbol CONFIG_ADFS_FS depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Symbol CONFIG_SOUND_RME96XX depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Symbol CONFIG_VIDEO_MEYE depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Symbol CONFIG_SONYPI depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Symbol CONFIG_MIDI_EMU10K1 depends on CONFIG_EXPERIMENTAL but does
not say so in its banner.

Two symbols CONFIG_ROADRUNNER and CONFIG_ROADRUNNER_LARGE_RINGS depend
on CONFIG_EXPERIMENTAL but do not say so in their banners.

The convention is that symbols that depend on $CONFIG_EXPERIMENTAL are
marked in the banner with the string (EXPERIMENTAL).  There are 4 cases
where that string is correctly used but is lowercase instead of uppercase.

The default value specified as the last word of the "choice" statement
should be a unique abbreviation of one of the sub-prompts, not some
random string never seen before.

Symbol CONFIG_ZNET depends on CONFIG_OBSOLETE, but its banner says it
depends on CONFIG_EXPERIMENTAL.

Symbol CONFIG_INTERMEZZO_FS depends on CONFIG_EXPERIMENTAL but does
not say so in its banner in the usual way.

The 2.4.18pre10 kernel, like many if its predecessors, can't compile
the multiquad driver in an SMP kernel (maybe only as a module; it's
been a long time since I wrote this fix).  Here's a patch.

When compiling 2.5.20 (and ealier, likely) without procfs, the declaration
for struct tty_driver is missing in proc_fs.h, causing many compiler warnings
that are fixed by this patch.

This micropatch adds unlikely() macro into add_timer() bug check code.
Without this path gcc 3.1 makes bad thing reordering printk() into
the middle of function body.

the following micro-patch changes ext[23]_ioctl to return EACCES
(permission denied) instead of EPERM (operation not permitted) if
the caller is not authorized to change the flags on a file.

  The following trivial patch makes the patch-kernel script executable by
  a bare bone POSIX shell like ash.  Either that, or the interpreter line
  has to be changed to /bin/bash.

  The same patch applies to 2.4 (with some line offset).