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

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

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

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

Make x86-64 compile again after recent extable changes.

Micheal Meeks notes:

	"Evolution is non-functioning on recent 2.5.X kernels, due to
    mal-performance in getpeername => net/unix/af_unix.c (unix_getname),
    where it seems we switch 'sk' on 'peer', but not the (previously)
    typecast pointer to it; this fixes it."

Whitespace fixes by Ray Lee.

and stop honoring the SA_RESTORER information.

This will prepare us for alternate signal handler returns.

Simply, pass off to kset_find_obj() to iterate over list of buses and 
search for bus with certain name.

The operation is simple:
- Take read lock for kset.
- Iterate over kset->list.
- Compare name to each kobject's name.
- Return kobject if found. 

This creates and exports device_bind_driver() and device_release_driver()
that allow a caller to manually bind a device to a driver. Apparantly, some
drivers use this functionality (like USB): a driver binds to other device
interfaces during the driver's probe() method call for the first interface.

Implementation is easy enough, since it simply involves renaming and exporting
the internal functions attach() and detach().

In drivers/base/bus.c, get_bus() was called without put_bus() in these 
functions:

- bus_for_each_dev()
- bus_for_each_drv()

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

- declare net_subsys, and register during net_dev_init().
- Add kobject to struct net_device.
- initialize name and register in register_netdevice().
- remove in unregister_netdevice().

This allows one to see the registered network devices in the system via:

# tree /sys/net/
/sys/net/
`-- eth0

Here are the i810 and i830 fixes.  I don't have either of these, so I
can't test them, but they're pretty straightforward.

I don't have a 440GX to test here, but I think the patch below is likely
to fix the problem.

I see some other issues in intel-agp.c.  I'll send those separately since
the diff is a little larger and should affect only i810 and i830.

Since block_subsys already contains a list and a lock, use those, instead
of defining our own static ones.

This allows struct gendisk::full_list to be removed. 

struct gendisk::list is also apparently unused, so it is removed also.

This was never used, and a bad idea to begin with. 

The kobject core no longer references a subsystem directly through a kobject,
instead using the kobject's dominant kset to reference the subsystem. The 
registrants of kobjects have been fixed up. 

To aid in this process, a few helpers were introdcuced: 

- kobj_set_kset_s(obj,subsys)
- kset_set_kset_s(obj,subsys)
- subsys_set_kset(obj,subsys)

that set the kset ptr of embedded kobjects for objects that have different
embedded types. See include/linux/kobject.h for more description and usage.


struct subsystem::kobj is also removed, relying solely on a subsystem's
embedded kset for hierarchy information.  Since this requires modification
of the subsystem declarations, a helper macro has been defined:

decl_subsys(name,type)

which initializes the name and ktype fields of the subsystem's embedded
kset. All the subsystem declarations have been fixed up.

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

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

Various archs (i386, m68k, s390, s390x, m68k, parisc, um, x86_64)
implement kernel_text_address.  Put this in kernel/extable.c, and the
module iteration inside module.c.

Other than cleanliness, this finally allows the module list and lock
to be static to kernel/module.c (you didn't think I actually cared
about those archs did you?)

It also drops the module->init_size to zero when it's discarded, so
bounds checking is simplified (and the /proc/modules size statistic
will be more accurate, too).

The declaration of `module_frob_arch_sections' in moduleloader.h (and
the definitions in most of the module.c files) are inconsistent with the
definition in the PPC's module.c -- in the latter the first two
arguments are not declared `const', whereas everyplace else they are.

PS.  secstrings can be modded to: if an arch can't handle discarding
     init, it simply renames the .init sections.

Oops in fb_set_cmap caused by palette_cmap.transp uninitialized.

By inspection, fb_blank appears to have the same problem.

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

This removes the agpgart assumption that memory is contiguous.

[Forward port of a 2.4 patch that got applied last month -- DJ] 
 
AGP/DRM currently assume that GATT entries can be converted
to physical addresses with a simple mask.  Additionally, agpgart
assumes in a couple places that the mask is ~0xfff, i.e., that
all the GART control bits are in the low 12 bits.  Both assumptions
are bogus, so:
  
Make agp_memory.memory[] (exported from agpgart to DRM) contain physical
addresses, not GATT entries.
  
DRM assumes agp_memory contains GATT entries, and it converts them to
physical addresses with "paddr = agp_memory.memory[i] & mask".  460GX
requires both a shift and a mask, so exporting plain physical addresses
and a mask of ~0UL allows agpgart to add 460GX support without requiring
DRM interface changes.

- global loops_per_jiffy, x86 cpu_khz and x86
   fast_gettimeoffset_quotient can only be safely adjusted on UP
- x86 per-CPU loops_per_jiffy does not depend on TSC
- save reference values so that rounding errors do not accumulate

Clean up searching code for best frequency multiplier, and add a
safety check. Also, SAFE_FREQ wasn't used.

The "get current speed" algorithm wasn't aware of the disable/enable bit,
and the policy verification function wasn't aware of the N44 / O17
bug. Also, some unused code is removed.

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

into are.twiddle.net:/home/rth/BK/axp-2.5

struct kset is what struct subsystem should have originally been called. It
is a set of kobjects, and nothing more, with a much less confusing name than
'subsystem.'

struct kset contains an embedded kobject, making it possible to represent it
in the object hierarchy, and sysfs. This also provides a means for objects
to easily express a list of subordinate objects. 

struct subsystem still exists, and contains an rwsem, which its subordinate
ksets use to protect their lists. 

An arbitrary number of ksets may belong to a subsystem. A ksets specifies
the subsystem it belongs to via its ->subsys field. 

struct subsystem also contains a default kset, which may be used without
having to define a separate kset. 

The objects that defined subordinate subsystems (bus and class drivers) have
been converted to use subordinate ksets instead.


Note that the usage of ksets is flexible. 
- ksets may contain a list of objects of any type, not just kobjects.
- The objects registered with a kset do not have to be registered.
- ksets themselves do not have to be registered. One can be used by
  simply calling kset_init(). 
- ksets do not need a name if they are not registered. 
- Note however that locking must be done manually in these cases.

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