ChangeSet@1.1806, 2004-04-15 11:57:06-07:00, geert@linux-m68k.org
  [PATCH] Amiga Zorro8390 Ethernet section conflict
  
  Jeff Garzik notes that the previous cleanup highlights a bug:
  >
  > 	static const struct card_info {
  > 	    zorro_id id;
  > 	    const char *name;
  > 	    unsigned int offset;
  > 	} cards[] __initdata = {
  >
  > and the lone user is __devinit:
  >
  > static int __devinit zorro8390_init_one(struct zorro_dev *z,
  >                                        const struct zorro_device_id *ent)
  
  Here's the fix..

ChangeSet@1.1805, 2004-04-15 11:56:52-07:00, James.Bottomley@SteelEye.com
  [PATCH] fix non-PC subarchs which were broken by i386 probe_roms change
  
  The author apparently didn't understand that only the mach-default
  include directory is included by fallback for header files only.  You
  can't stick a .c file in mach-default and expect all subarchs to be able
  to use it.
  
  The correct fix is to put std_resources.c in the kernel directory and
  give it its own Kconfig symbol for conditional compile so that subarchs
  may choose to include it or not.

ChangeSet@1.1804, 2004-04-15 10:29:23-07:00, xschmi00@stud.feec.vutbr.cz
  [PATCH] USB: Fix vicam debug compile, fix user access
  
  The last copy_from_user patch to the vicam driver broke compilation with
  VICAM_DEBUG on.
  
  There is also another copy_from_user missing in case VIDIOCSPICT. 
  
  This fixes both issues.

ChangeSet@1.1801.1.1, 2004-04-15 09:20:00-07:00, James.Bottomley@SteelEye.com
  [PATCH] fix 4k irqstacks on x86 (and add voyager support)
  
  There's a bug in the x86 code in that it sets the boot CPU to zero.
  
  This isn't correct since some subarch's use physically indexed CPUs. 
  However, subarchs have either set the boot cpu before irq_INIT() (or
  just inherited the default zero from INIT_THREAD_INFO()), so it's safe
  to believe current_thread_info()->cpu about the boot cpu.

ChangeSet@1.1802, 2004-04-15 08:22:54-07:00, greg@kroah.com
  merge

ChangeSet@1.1801, 2004-04-15 07:04:22-07:00, benh@kernel.crashing.org
  [PATCH] ppc64: update g5_defconfig
  
  This adds IOMMU support & IOMU virtual merging to the default g5 config.
  
  This will not impair performances of machines that don't need the iommu
  (the kernel will only enable it if you have more than 2Gb of RAM, though
  you can explicitely enable it using a command line argument).

ChangeSet@1.1800, 2004-04-15 07:04:10-07:00, benh@kernel.crashing.org
  [PATCH] ppc64: Fix possible duplicate MMU hash entries
  
  The current code has a subtle race where 2 hash PTEs can be inserted
  for the same virtual address for a short period of time. There should
  not be a stale one as the "old" one ultimately gets flushed, but the
  architecture specifies that having two hash PTE is illegal and can
  result in undefined behaviour.
  
  This patch fixes it by never clearing the _PAGE_HASHPTE bit when
  doing test_and_clear_{young,dirty}. That means that subsequent faults
  on those pages will have a bit more overhead to "discover" that the
  hash entry was indeed evicted.
  
  It also adds a small optisation to avoid doing the atomic operation
  and the hash flush in test_and_clear_dirty when the page isn't dirty
  or when setting write protect while it's already set.

ChangeSet@1.1799, 2004-04-15 07:03:54-07:00, akpm@osdl.org
  [PATCH] posix messages queues for s390.
  
  From: Martin Schwidefsky <schwidefsky@de.ibm.com>
  
  The new message queue interface needs the following patch to get it working
  on s390 (31-bit, 64-bit and 31-bit compat).

ChangeSet@1.1798, 2004-04-15 07:03:43-07:00, akpm@osdl.org
  [PATCH] light-weight auditing framework for s390.
  
  From: Martin Schwidefsky <schwidefsky@de.ibm.com>
  
  This patch adds the TIF_SYSCALL_AUDIT option to the s390 ptrace interface.

ChangeSet@1.1797, 2004-04-15 07:03:32-07:00, akpm@osdl.org
  [PATCH] Add mqueue support to x86-64
  
  From: Andi Kleen <ak@suse.de>
  
  Add POSIX mqueue support to x86-64.

ChangeSet@1.1796, 2004-04-15 07:03:20-07:00, akpm@osdl.org
  [PATCH] ext3: journalled quotas
  
  From: Jan Kara <jack@ucw.cz>
  
  Journalled quota support for ext3: The patch consists of two parts - ext3
  changes and changes in generic quota code.  The main idea of the changes is
  that a transaction is always started before any operation which changes quota
  file and dirtifying of the quota causes its write to disk.  These two changes
  assure that quota change is journalled into the same transaction as the file
  change and hence after journal replay quota is consistent with the filesystem
  state.  As during journal replay inodes from orphan list are deleted/truncated
  we have to do quota_on before the replay of the orphan list - this problem is
  solved by additional mount options to ext3 with quota file names and format.
  
  Some changes in generic code were also needed to assure that quota structure
  in file is always allocated and so ordinary quota operations (like
  adding/deleting a block/inode) need only a few blocks from the transaction.

ChangeSet@1.1795, 2004-04-15 07:03:05-07:00, akpm@osdl.org
  [PATCH] mq_open() and close_on_exec
  
  From: Chris Wright <chrisw@osdl.org>
  
  SUSv3 doesn't seem to specify one way or the other.  I don't have the POSIX
  specs, and the old docs I have suggest that mq_open() creates an object
  which is to be closed upon exec.
  
  Jakub said:
  
    I think it is valid and required:
  
      http://www.opengroup.org/onlinepubs/007904975/functions/exec.html
  
      All open message queue descriptors in the calling process shall be
      closed, as described in mq_close()
  
    I'll add a new test for this into glibc testsuite.

ChangeSet@1.1794, 2004-04-15 07:02:51-07:00, akpm@osdl.org
  [PATCH] radix-tree comment fix
  
  Fix various bogons and outright lies.

ChangeSet@1.1793, 2004-04-15 07:02:37-07:00, akpm@osdl.org
  [PATCH] Fix mq_notify with SIGEV_NONE notification
  
  From: Jakub Jelinek <jakub@redhat.com>
  
  	mq_notify (q, NULL)
  
  and
  	struct sigevent ev = { .sigev_notify = SIGEV_NONE };
  	mq_notify (q, &ev)
  
  are not the same thing in POSIX, yet the kernel treats them the same.  Only
  the former makes the notification available to other processes immediately,
  see
  
  	http://www.opengroup.org/onlinepubs/007904975/functions/mq_notify.html
  
  Without the patch below,
  
  	http://sources.redhat.com/ml/libc-hacker/2004-04/msg00028.html
  
  glibc test fails.
  
  I looked at mq in Solaris and they behave the same in this regard as Linux
  with this patch.  Kernel with this patch passes both Intel POSIX testsuite
  (with testsuite fixes from Ulrich) and glibc mq testsuite.

ChangeSet@1.1790.1.11, 2004-04-14 18:31:20-07:00, torvalds@ppc970.osdl.org
  Linux 2.6.6-rc1
  TAG: v2.6.6-rc1