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.

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.

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

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

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

1. All the memory barriers are SMP-only avoiding unnecessary overhead on UP.
2, My forward porting merge of the rt_rcu patch dropped two changes in
   rt_intern_hash() in around 2.5.43 that ordered the writes while
   inserting a dst entry at the start of a hash chain. The dst entry updates
   must be visible to other (weakly ordered) CPUs before it is inserted.
   The necessary smp_wmb()s are added.
3. Comments to go with the write ordering.

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

  As part of the Linux Kernel Janitors project, I would like to submit my
  patch for sa1100_ir.c.

  The document Documentation/cli-sti-removal.txt says that cli() should no
  longer be used to disable interrupts. This patch removes the last
  references to cli() and {save,restore}_flags, changing them to
  local_irq_save and local_irq_restore respectively.

  This patch for saphir.c isdn driver for Linux removes one call to
  check_region using request_region instead

  I don't have this hardware so patch is not tested at all (I hope I got
  it right).  This patch removes all references to check_region in this
  driver.

  This is patch number 11 in a series of check_region patches I am doing
  as part of the kernel janitors project.

  As part of my work on the Linux Kernel Janitors project, cleaning up on
  functions which call misc_register and don't check for an error
  return, I would like to submit my patch to drivers/sgi/char/usema.c

  This module did not check the return code of misc_register. I found Uttam
  Pawar's patch for this on GeoCrawler
  (http://www.geocrawler.com/archives/3/9221/2002/8/0/9246517/), but it
  doesn't appear to have been applied. This patch basically does exactly the
  same as his, so all credit is due to him.

  This patch for Documentation/DocBook/videobook.tmpl removes two
  references check_region in the documentation using request_region
  instead.

  This patch removes all references to check_region in videobook.tmpl

  This is patch number 29 in a series of check_region patches I am doing as
  part of the kernel janitors project.