Re: [PATCH][1/2] fix for -mm add-sem_is_read-write_locked.patch

Rik van Riel <[email protected]> wrote:

> I really shouldn't make patches like this in the morning on weekends, 
> when I'm still sleepy.  Well, here is the trivial fix...

That would seem to fix that bit.

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- Re: [PATCH][1/2] fix for -mm add-sem_is_read-write_locked.patch
  - From: Rik van Riel <[email protected]>
- Re: [PATCH][1/2] fix for -mm add-sem_is_read-write_locked.patch
  - From: David Howells <[email protected]>

Prev by Date: Re: [ATMSAR] Request for review - update #1
Next by Date: Re: 2.6.13 (was 2.6.11.11) and rsync oops (SATA or NFS related?)
Previous by thread: Re: [PATCH][1/2] fix for -mm add-sem_is_read-write_locked.patch
Next by thread: PROBLEM: kexec -p fails with: Invalid memory segment 0x100000 - 0x3b6fff
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind]