From: Gerd Knorr <kraxel@bytesex.org>

Use module_param() rather than the deprecated MODULE_PARM() in this driver.

From: Jes Sorensen <jes@trained-monkey.org>

The new sort_extable and shared search_extable code doesn't work on ia64.
I have introduced two new #defines that archs can define to avoid the
common code being built.  ARCH_HAS_SEARCH_EXTABLE and
ARCH_HAS_SORT_EXTABLE.

From: David Howells <dhowells@redhat.com>

Eliminate the printing of the cache token if present: using cpp
conditionals inside macro expansions is not legal and some gcc's fail it.

From: Steve Dickson <SteveD@redhat.com>

Here is a patch for the 2.6.1 kernel that fixes an oops that occurs when
the sunrpc module is unloaded.

The problem was the RPC cache_register() call was not saving entry pointers
to the procfs entries it was creating.  So when it came time to dismantle
the entires, a BUG_ON() was tripped in remove_proc_entry() since the tree
was not broken down completely.

(acked by neilb)

These printk's come out during normal usage, when accessing locked system
files on the windows machines.

From: Jan Kara <jack@ucw.cz>

A patch which fixes a problem that i_blocks are not updated for quota files
(when quota turned on) in 2.6.1.  The patch also fixes possible unlock of
not locked spin_lock.

Ratelimit a couple of potentially-stormy printk's in the writeback code.

From: Petri Koistinen <petri.koistinen@iki.fi>

Little URL fix.  Server requires www in front of URL, no automatic
forwarding.

From: Vojtech Pavlik <vojtech@suse.cz>

From: Nikita Danilov <Nikita@Namesys.COM>

fs/reiserfs/journal.c:cleanup_bitmap_list() can be called to cleanup
reiserfs_list_bitmap that was only partly initialized. Check that
jb->bitmaps array was actually allocated, before trying to free its
elements.

The exception table search code currently fails if addresses differ by more
than 2G.  This is only a problem when using the 4g/4g address space split,
but it's more robust this way.

Also, shuffle the comparison order n there so the least likely case comes
last.

From: Jan Kara <jack@suse.cz>

Journalled-data files need a different set of address_space_operations, so
we need to update the file's aops when someone runs `chattr +j' on the
file.

From: "Randy.Dunlap" <rddunlap@osdl.org>

This patch changes no code, just swaps macro arg names to match reality.

From: "Randy.Dunlap" <rddunlap@osdl.org>
From: Michael Still <mikal@stillhq.com>

Viro and Andi Kleen agreed.  The <flags> argument isn't used at all and
cannot be used safely in the future.

remove third arg <long flags> from all 3 fs/stat.c stat64() calls since
it's not used and there's no way to use it safely;

From: "Randy.Dunlap" <rddunlap@osdl.org>
From: Luiz Fernando Capitulino <lcapitulino@prefeitura.sp.gov.br>

This #ifdef/#endif is not necessary.

From: "Randy.Dunlap" <rddunlap@osdl.org>
From: Andreas Beckmann <sparclinux@abeckmann.de>

Patch is for consistency in spelling Unix98 (vs.  Unix 98).  This matches
the other 20 or so occurrences of it.

From: "Randy.Dunlap" <rddunlap@osdl.org>
From: Patrick McLean <pmclean@linuxfreak.ca>

From: "Randy.Dunlap" <rddunlap@osdl.org>
From: Luiz Fernando Capitulino <lcapitulino@prefeitura.sp.gov.br>

It fixes these warnings when !CONFIG_PROC_FS:

drivers/md/md.c: In function `md_geninit':
drivers/md/md.c:3481: warning: unused variable `p'
drivers/md/md.c: At top level:
drivers/md/md.c:3007: warning: `md_seq_fops' defined but not used

From: "Randy.Dunlap" <rddunlap@osdl.org>
From: Eugene TEO <eugeneteo@eugeneteo.net>

Handle OOM in mca_init()

From: "Randy.Dunlap" <rddunlap@osdl.org>
From: Eugene TEO <eugeneteo@eugeneteo.net>

From: "Randy.Dunlap" <rddunlap@osdl.org>
From: Luiz Fernando Capitulino <lcapitulino@prefeitura.sp.gov.br>

this patch fixes this warning:

drivers/ide/pci/amd74xx.c:80: warning: `amd_udma2cyc' defined
but not used

when !CONFIG_PROC_FS.

From: Michael Hunold <hunold@linuxtv.org>

- TTUSB-DEC update by Alex Woods:

  - fix USB timeout bug under 2.6

  - change some variable names to make it clearer what we are dealing
    with (PVA).  - support DEC2540-t and add info on it to the ttusb-dec
    docs.

  - add model number returned from DEC2540-t firmware.

  - add a module option to get the raw AVPES packets from the dvr
    device.

  - send audio packets to their filter rather than the videos.

  - handle the new empty packets that appear with the 2.16 firmware.

  - extra error checks.

  - handle the new firmwares that change the devices' USB IDs.

  - tidy up the STB initialisation process a little.

  - apply Hans-Frieder Vogt's patch for calculating firmware CRCs.

- make TTUSB budget card depend on USB subsystem

From: Michael Hunold <hunold@linuxtv.org>

- after the firmware removal, split av7110.c into separate modules:

  - av7110.c: initialization and demux stuff

  - av7110_hw.c: lowlevel hardware access and firmware interface

  - av7110_ca.c: CI and ECD

  - av7110_av.c: audio/video MPEG decoder and remuxing stuff

  - av7110_v4l.c: v4l interface

- av7110 fixes that were notcies during splitup

  - rename some non-static functions to enhance readability

  - lots of coding style & whitespace fixes

  - return -ERESTARTSYS from ci_ll_read/write() if interrupted

  - use time_after() for timeouts

  - added some comments about firmware interface

  - removed some unused fields from struct av7110, retabbing

- follow driver splitup in Makefile

From: Michael Hunold <hunold@linuxtv.org>

- demux: fix nasty bug where setting multiple filters resulted in ts
  packet duplication

- frontend: merge frontend improvements from 2.4 DVB tree:

  - schedule_timeout(1) in dvb_frontend.c after setting frontend and
    before waking up frontend thread

  - do FE_RESET in each iteration of frontend thread if !FE_HAS_LOCK

  - use aquire_signal flag to call FE_RESET only after tuning until
    FE_HAS_LOCK has been signalled, and not when FE_HAS_LOCK drops out for
    short periods of time later

- follow frontend changes in ves1x93 driver

From: Michael Hunold <hunold@linuxtv.org>

- fix memory leak in page table handling

- minor coding style changes

- add simple resource management for video dmas (borrowed from saa7134)

- use resource management to lock video and vbi access which sometimes
  share the same video dmas

- honour return codes of extension functions in various places, when
  resources could not be locked

- remove remains of dead code which were commented out anyway

- add new flag FORMAT_IS_PLANAR to indicate planar capture formats,
  needed for resource allocation

From: Michael Hunold <hunold@linuxtv.org>

- update contributors

- documentation update for recent DVB TTUSB driver changes

From: Russell King <rmk+lkml@arm.linux.org.uk>

Russell was unable to correctly migrate this driver to the new
modem-control-signal API because

 TIOCMBIS/TIOCMBIC do not control only the DTR signal, but also the RTS,
 OUT1 and OUT2 signals, or even maybe nothing at all.  Plus, these IOCTLs
 are no longer passed down to the driver.  Instead, drivers should
 implement tiocmget and tiocmset driver methods.

so mark it as broken so as to not break allmodconfig/allyesconfig.

From: Manfred Spraul <manfred@colorfullife.com>

sendfile supports reading from a given start offset for in_file, like
pread.  But for the locks_verify_area call, in_file->f_pos is always used,
even if a start offset is used.  Result: wrong area is checked for
mandatory locks.

From: Andi Kleen <ak@muc.de>

The EFLAGS checking was not correct.  This also fixes some problems with
32bit gdb who would sometimes make the kernel BUG.

From: Chris Wright <chrisw@osdl.org>

Add default hooks for both the dummy and capability code to protect the
XATTR_SECURITY_PREFIX namespace.  These EAs were fully accessible to
unauthorized users, so a user that rebooted from an SELinux kernel to a
default kernel would leave those critical EAs unprotected.

(Acked by Stephen Smalley)

From: Chris Wright <chrisw@osdl.org>

Move the XATTR_SECURITY_PREFIX macro to the xattr.h header so that it's in a
common location.

(Acked by Stephen Smalley)

From: NeilBrown <neilb@cse.unsw.edu.au>

..to access 'mddev' from the inode pointer.  This is already set up for us.

From: NeilBrown <neilb@cse.unsw.edu.au>

We only need it occasionally to map unit number to mddev, and we can use a
linear search for that.  This reduces dependance on MAX_MD_DEVS

From: NeilBrown <neilb@cse.unsw.edu.au>

Move the pointers into mddev.  The reduces dependance on MAX_MD_DEVS.

From: NeilBrown <neilb@cse.unsw.edu.au>

Currently a raid0 superblock is only written when the array is stopped, so a
crash between creation and stop can lose your data.

This patch marks a superblock 'dirty' at creation and forces a dirty
superblock to be written when the array is started.

Previously we would prod the per-array thread at this point, but as it avoids
certain chores when the array is locked, and the array is locked at this
point, that isn't guaranteed to do the right thing.  Instead we prod the
thread whenever the array is unlocked.

Finally, only write the superblock at array stop if it is needed to mark the
array as 'clean'.  raid0 which is never dirty, doesn't need this.

From: NeilBrown <neilb@cse.unsw.edu.au>

Current code calls do_md_stop to clean up if do_md_run fails, but this is

a/ not needed as do_md_run cleans up itself

b/ bad as it could try to clean up after an -EBUSY error !!!

From: NeilBrown <neilb@cse.unsw.edu.au>

Currently if there are two failed drives, and two spares are added, then
recovery starts onto the first spare, but never notices the second spare.  To
cope, we set RECOVERY_NEEDED when recovery finishes so that we re-check.

From: NeilBrown <neilb@cse.unsw.edu.au>

Thanks dann frazier <dannf@hp.com>

From: NeilBrown <neilb@cse.unsw.edu.au>

If the raid1 or raid5 thread gets to run md_check_recovery after the recovery
thread has been interupted, but before do_md_stop completes, a spare drive
can be incorporated into an array befure it is up-to-date.

This patch corrects the relevant test.

From: NeilBrown <neilb@cse.unsw.edu.au>

raid5 rebuild takes stripes so agressively that other access cannot get a
look-in.

With this patch, the rebuild pauses slightly if there is a shortage of
stripes to let other processes have a chance.

akpm: I was worried about starvation due to the harsh semantics of yield() in
2.6.  But Neil has performed specific testing for that and things seem OK. 
If people do note CPU starvation problems we will need to replace the yield()
with a schedule_timeout(1).