- rename at_addr to atalk_addr, netrange to atalk_netrange
- use kerneldoc style comments for some structs and functions
- move the IP over DDP handling code out of atalk_rcv into handle_ip_over_ddp,
  that is optimized out when this feature was not selected by the user
- move the routing handling code out of atalk_rcv into atalk_route_packets
- create ddp_hdr and aarp_hdr inline functions to access those protocol headers
  on the skb
- lots of CodingStyle cleanups

into home.transmeta.com:/home/torvalds/v2.5/linux

into home.transmeta.com:/home/torvalds/v2.5/linux

into nuts.ninka.net:/home/davem/src/BK/net-2.5

Earlier Intel CPUs didn't have the cpuid namestring feature,
so we have to look them up in tables..

Fix by Patrick Mochel.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

Cset exclude: torvalds@home.transmeta.com|ChangeSet|20020801011106|51286

we are starting to split gendisks - now we can do that.  Done for
ide, sd, pd, hd and mfm

It's in transit - what we are aiming at is getting ->nr_real to 1 for
all gendisks.  Once that will be done we will be able to simplify a lot
stuff and remove ad-hackery.  First thing that will happen after that
is death of ->nr_real, obviouslye.  Then we
	(a) will merge ->major and ->first_minor into ->dev
	(b) strip one level of indirection from  ->driverfs_dev_arr, ->de_arr
and ->flags - they turn into single-element arrays and we will simply pull
the (only) element into struct gendisk.  Kills a lot of ad-hackery in splitup
code (fewer things to allocate).
	(c) replace ->major_name with ->disk_name; kills most of the crap in
disk_name(9) - it only has to care about adding partition number to the name.

now that gendisks don't have shared stuff (we used to set blk_size[]
from ->sizes) we can start splitting them into per-disk ones.

Step 1:
  we introduce a new field - ->first_minor (to be merged with ->major
  into dev_t of entire disk once all gendisks are split).  All arrays
  are assumed to start at that minor (i.e.  gd->part[minor] got replaced
  with gd->part[minor - gd->first_minor], etc.).  get_gendisk() is
  taught to pick the right gendisk if there are several with the same
  major.

kills use of blk_size[] for partitioned devices, removes ->sizes from
struct gendisk.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

This patch corrects a comment on the 8139cp ethernet driver.

This removes the TLS clear operation.  I've left the flags mask and the
writable flag just so that we have the option to introduce extensions
without breaking the ABI.

this is a small patch for boardergo.c linux driver for isdn HYSDN cards to
    1) remove call to check_region using request_region instead
    2) check the status of call to request_region
    3) release allocated region resource in case of error.

I don't have this hardware so compilation checked only.

from Debian's kernel package

[ Typo fix, makes sense, please apply ]

Symbols CONFIG_HISAX_ENTERNOW_PCI and CONFIG_HISAX_AMD7930 depend on
CONFIG_EXPERIMENTAL but do not say so in their banners.

Symbol CONFIG_PPPOATM doesn't depend on CONFIG_EXPERIMENTAL but claims
to in its banner.

Somebody noticed on #kernelnewbies. In the error path, so this is
silly cleanup work...

Some CML1 rule contributors seem to think that the "bool" statement
takes a third argument which is the default value.  It doesn't.

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-driverfs-api

I am not sure if you are the actual maintainer for this, but your name
adorns the source :
  2.5.28 introduced video mode 1400x1050 twice into drivers/video/modedb.c
Both instances use indentical timings, so I guess it's a mistake.

Symbol CONFIG_EXT3_FS doesn't depend on CONFIG_EXPERIMENTAL but claims
to in its banner.

Quick fix for:
  smbiod.c:272: warning: deprecated use of label at end of compound statement

this is a small patch for baycom_ser_hdx.c  -- baycom ser12 halfduplex radio modem driver to
    1) remove call to check_region using request_region instead
    2) check the status of call to request_region
    3) release allocated region resource in case of error.

I don't have this hardware so compilation checked only.

They are harmless mostly and can happen in normal use. (from -rh)