The m68k architecture define is __mc68000__, not __m68k__.

From Andreas Schwab <schwab@suse.de>.

  Fix undefined symbol references when support for G100 is requested,
but support for G450 is not.

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

into kleikamp.austin.ibm.com:/home/shaggy/bk/jfs-2.5

If the log (journal) superblock is changed between the time we mount
and unmount the volume, don't trap.  Instead complain, and exit
gracefully.

Always free the request, not just on error.

Small problem, we must of course also remember to take into account
where the last service point was (or will be).

deadline_get_last_sector() either returns the last offset serviced, or
the last one that will be (back of dispatch queue).

Otherwise the insert-at-head can be very unfair.

  Jens Thoms Toerring <Jens.Toerring@physik.fu-berlin.de>
    - RDP must be reset only in isolation phase

It appears that during the MODULE_LICENSE merge for pcmcia i82092 was
missed.

Here is a trivial patch to correct this.

This fixes a problem with the deadline io scheduler, if the correct
insertion point is at the front of the list.  This is something that we
never have gotten right in 2.4 either.

The problem is that the elevator merge function has to return a pointer
to a struct request, and for front insert we really have to return the
head of the list which cannot be expressed as a request of course.

The real issue is that the elevator_merge function actually performs two
functions - it scans for a merge, and if it can't find any, it selects
and insertion point.  It's done this way for efficiency reasons, even if
the design isn't all that clean.

So we change the io scheduler merge functions to get passed a pointer to
a list_head pointer instead.  This works for both inserts and merges.
In addition, deadline checks if it really should insert at the very
front.

Also don't pass in request to elv_try_last_merge(), the very name of the
function suggests that it's q->last_merge that we are interested in.

- XFS has started to use clear_page_dirty(), so we should export
  test_clear_page_dirty() to modules.

  This function is ued by the inlined clear_page_dirty().  It marks a
  page clean and updates the global dirty memory accounting.  Anyone
  who cleans pagecache pages should use this, so the export makes
  sense.  Can't implement aops->writepages() without it, really.

- __mark_inode_dirty is no longer called under mapping->private_lock.
   Update comment.

This updates the orinoco wireless driver to version 0.13.

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

That saves space in the generated binaries and make it easier to
drop the lock just in one place.

Typedefs can't be forward declared, so we prefer structs, that can.

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

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

having a valid name (base kernel: "").

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

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

Make the kernel print out symbolic bactraces if symbol table information
is available (CONFIG_KALLSYMS)

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

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

when it is explicitly overridden in the MADT

The directory index values are the unique cookies used to resume
a readdir at the proper place.  These are stored with each entry
in a directory.  fsck.jfs does not currently validate these entries,
nor even create them when populating the lost+found directory.

This patch causes readdir to detect the invalid cookies, and generate
new ones, if possible.

Modid: 2.5.x-xfs:slinx:128467a

Modid: 2.5.x-xfs:slinx:128366a

Modid: 2.5.x-xfs:slinx:128363a

Modid: 2.5.x-xfs:slinx:128239a

Modid: 2.5.x-xfs:slinx:128192a