into tiger.hpl.hp.com:/data1/bk/lia64/to-linus-2.5

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

proc_bus_pci_dir had to be exported for this to work properly.

      
Patch based on work done by Irene Zubarev <zubarev@us.ibm.com>

it might be actively running on another CPU, so we still need to
do the synchronous wait.

I've been working on a userspace daemon to go with my CompactPCI driver,
and yesterday I discovered an oversight in pci_hp_change_slot_info - it
doesn't call dnotify_parent, so dnotify based clients basically don't
work against pcihpfs.  The following patch (against 2.5 BK) reworks
things to just update the mtime (since we're modifying the file after
all), and then call dnotify_parent.

These are the debated tty_io.c changes to use the session group lists to
maintain controlling tty information.

This is the latest version of the generic pidhash patch.  The biggest
change is the removal of separately allocated pid structures: they are
now part of the task structure and the first task that uses a PID will
provide the pid structure.  Task refcounting is used to avoid the
freeing of the task structure before every member of a process group or
session has exited.

This approach has a number of advantages besides the performance gains.
Besides simplifying the whole hashing code significantly, attach_pid()
is now fundamentally atomic and can be called during create_process()
without worrying about task-list side-effects.  It does not have to
re-search the pidhash to find out about raced PID-adding either, and
attach_pid() cannot fail due to OOM.  detach_pid() can do a simple
put_task_struct() instead of the kmem_cache_free().

The only minimal downside is the potential pending task structures after
session leaders or group leaders have exited - but the number of orphan
sessions and process groups is usually very low - and even if it's
higher, this can be regarded as a slow execution of the final
deallocation of the session leader, not some additional burden.

lists by default. The batching avoids some debug tests.

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

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

For some inexplicable reason, I broke the dependency on a new build number
some time ago - it worked fine before, and now it does again.

(Whenever vmlinux is relinked, the build number is incremented, and now it
ends in the version string again, as it should)

Noted by Anton Blanchard.

ide_toggle_bounce() was called prior to init'ing the block queue,
which then reset the bounce_pfn back to BLK_BOUNCE_HIGH. Make
ide_toggle_bounce() an ide-lib helper, and call it when setting up
the queue as well.

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5

by making 'smc_init' static.

Also, some cleanups.

s/insl_unswapped/insl_ns/ inside #ifdef __powerpc__

* add EISA 10/100 card id
* properly align rx skbs

device and protocol attach/detach support.

Overall, this is in preparation for update of HDLC API

linux-wlan-ng sources and online sources

MOD_{INC,DEC}_USE_COUNT, eliminating a small race

(contributed by matthias@waechter.wiz.at)

compile-enabled nor compileable in ages.

(originally by Arjan, merged and re-merged by hch)

it uses the following test to determine whether the timeout has
expired:

        if (jiffies - dma_start > PCNET_RDC_TIMEOUT) {

Unfortunately, PCNET_RDC_TIMEOUT is defined to be "0x02", so the
length of the timeout is only two jiffy ticks, rather than being
the expected 20ms.  This patch fixes this.

Also, the above (and one other place) should be converted to
time_after().

rid of save_flags();cli();. I was pleasantly surprised that the driver
was working fine on my SMP system with those obvious fixes. Tested on
2.5.32 SMP.

- Set dev->trans_start to avoid filling the logs
	(and generating useless abort commands)
- Avoid deadlocks in mmc_out()/mmc_in()

- Set dev->trans_start to avoid filling the logs
- Handle better spurious/bogus interrupt
- Avoid deadlocks in mmc_out()/mmc_in()

for the HostAP driver, with few cleanups and new unused
definitions. The most contention change is that this version now
requires user space to provide the buffer size when making a GET (to
check buffer overrun), which will break very old version of Wireless
Tools (v22 and earlier).

that are used in natsemi net driver

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5

Andrew found out that bounce end_io handling did not work for him, so I
fixed the bug (not consistent checking of bi_size). I cleaned it up and
moved the bi_size checking out of bounce_end_io() (the main worker) and
into the individual bi_end_io() handlers instead. Please apply to make
highmem bouncing work again.

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5