> That's what you are going to have to set the name file to in the
> i2c_client structure, much like your patch did.  Then look at the
> different name files in each device directory to see what kind of device
> it is (chip, subclient, etc.)

OK attached patch sets all names to just chip name for chips themselves and
"chipname subclient" when subclient ios registered.

Fix bug when registering the i2c_adap as the structure was not set to 0.

Remove direct memory accesses and link up device in the proper place in the
sysfs tree.

This is based on the lmsensor cvs version of the driver, but is cleaned
it up and ported it to 2.6.

This is based on the lmsensor cvs version of the driver, but is cleaned
it up and ported it to 2.6.

This is based on the lmsensor cvs version of the driver, but is cleaned
it up and ported it to 2.6.

remove unnecessary version.h from drivers/i2c.
test compiled with 2.6.0-test5-bk2 on x86.

This updates the current 2.6 PPC 4xx driver to the rewritten version
we have in the PPC development tree.  It is cleaner, has less bugs,
and has more features.

Forgot to do this before...

This is based on the lmsensor cvs version of the driver, but is cleaned
it up and ported it to 2.6.

This is based on the lmsensor cvs version of the driver, but is cleaned
it up and ported it to 2.6.

This is based on the lmsensor cvs version of the driver, but is cleaned
it up and ported it to 2.6.

into kroah.com:/home/greg/linux/BK/i2c-2.6

Seems i2c_adapter.id is only used in some video drivers, will work on
cleaning up that mess later...

into home.osdl.org:/home/torvalds/v2.5/linux

into kernel.bkbits.net:/home/davem/sparc-2.5

into kernel.bkbits.net:/home/davem/net-2.5

Harald synced up ipt_REJECT.c from 2.4 route fixes, but it had
changed a fair bit because of the nonlinear fixes.  This repairs it.

1) Copying of tcp header onto stack.
2) ...which also checks length requirement.
3) Skip checksum check: requires linear packet.

Herve Eychenne noted that many ADSL connections get the same
address when the interface comes back up, so some users use SNAT
instead of masquerade.  The answer is that MASQUERADE should only
drop connections when the interface comes up, and then only if the
interface address has actually changed.