[PATCH] [JANITOR] Actually use the calculated cnt in kernel/trace/ring_buffer.c

Was deleting an old github kernel tree and noticed this one line patch I had made years back. Can't remember the compiler warning anymore but clearly it complained about pointless assigment to cnt since it is not used after that, although to me it looks like it should. Signed-off-by: Mika

[PATCH] [JANITOR] Actually use the calculated cnt in kernel/trace/ring_buffer.c

Was deleting an old github kernel tree and noticed this one line patch I had made years back. Can't remember the compiler warning anymore but clearly it complained about pointless assigment to cnt since it is not used after that, although to me it looks like it should. Signed-off-by: Mika

[PATCH] Couple fixes to fs/ecryptfs/inode.c

check. Signed-off-by: Mika Kukkonen <[EMAIL PROTECTED]> diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c index 1548be2..d230a48 100644 --- a/fs/ecryptfs/inode.c +++ b/fs/ecryptfs/inode.c @@ -282,7 +282,7 @@ static struct dentry *ecryptfs_lookup(struct inode *dir, struct dentry *dentry,

[PATCH] Fix bug in mm/thrash.c function grab_swap_token()

lan. Attached patch (compile tested) reverses the order. Btw, I'm not sure if likely() makes any sense in this new situation. Signed-off-by: Mika Kukkonen <[EMAIL PROTECTED]> diff --git a/mm/thrash.c b/mm/thrash.c index 9ef9071..c4c5205 100644 --- a/mm/thrash.c +++ b/mm/thrash.c @@ -48,9 +48,

[PATCH] Bug in fs/afs/write.c function afs_write_back_from_locked_page()

s I can see. Trival fix attached (compile tested only). Signed-Off-By: Mika Kukkonen <[EMAIL PROTECTED]> diff --git a/fs/afs/write.c b/fs/afs/write.c index 83ff292..4bca263 100644 --- a/fs/afs/write.c +++ b/fs/afs/write.c @@ -395,8 +395,9 @@ static int afs_write_back_from_locked_pa

[PATCH] Bug in fs/afs/write.c function afs_write_back_from_locked_page()

can see. Trival fix attached (compile tested only). Signed-Off-By: Mika Kukkonen [EMAIL PROTECTED] diff --git a/fs/afs/write.c b/fs/afs/write.c index 83ff292..4bca263 100644 --- a/fs/afs/write.c +++ b/fs/afs/write.c @@ -395,8 +395,9 @@ static int afs_write_back_from_locked_page(struct

[PATCH] Fix bug in mm/thrash.c function grab_swap_token()

. Attached patch (compile tested) reverses the order. Btw, I'm not sure if likely() makes any sense in this new situation. Signed-off-by: Mika Kukkonen [EMAIL PROTECTED] diff --git a/mm/thrash.c b/mm/thrash.c index 9ef9071..c4c5205 100644 --- a/mm/thrash.c +++ b/mm/thrash.c @@ -48,9 +48,8 @@ void

[PATCH] Couple fixes to fs/ecryptfs/inode.c

-off-by: Mika Kukkonen [EMAIL PROTECTED] diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c index 1548be2..d230a48 100644 --- a/fs/ecryptfs/inode.c +++ b/fs/ecryptfs/inode.c @@ -282,7 +282,7 @@ static struct dentry *ecryptfs_lookup(struct inode *dir, struct dentry *dentry, struct

[PATCH] Fix kernel build with EMBEDDED & PROC_FS & !PROC_SYSCTL

Without attached patch against current -git I get following with !PROC_SYSCTL (with EMBEDDED and PROC_FS set): CC init/version.o LD init/built-in.o LD vmlinux fs/built-in.o: In function `do_proc_sys_lookup': proc_sysctl.c:(.text+0x26583): undefined reference to

[PATCH] Fix kernel build with EMBEDDED PROC_FS !PROC_SYSCTL

Without attached patch against current -git I get following with !PROC_SYSCTL (with EMBEDDED and PROC_FS set): CC init/version.o LD init/built-in.o LD vmlinux fs/built-in.o: In function `do_proc_sys_lookup': proc_sysctl.c:(.text+0x26583): undefined reference to

[PATCH] Minor fix to kernel/workqueue.c

turns NULL, not negative pointer (duh!), so following trivial patch suggests itself. Signed-off-by: Mika Kukkonen <[EMAIL PROTECTED]> --- linux-2.6.orig/kernel/workqueue.c 2005-08-03 22:17:33.296479048 +0300 +++ linux-2.6/kernel/workqueue.c2005-08-03 22:30:11.960984648 +0300

[PATCH] Minor fix to kernel/workqueue.c

, not negative pointer (duh!), so following trivial patch suggests itself. Signed-off-by: Mika Kukkonen [EMAIL PROTECTED] --- linux-2.6.orig/kernel/workqueue.c 2005-08-03 22:17:33.296479048 +0300 +++ linux-2.6/kernel/workqueue.c2005-08-03 22:30:11.960984648 +0300 @@ -501,7 +501,7

[PATCH] Fix compile warning in drivers/pnp/resource.c with !CONFIG_PCI

outside this one other place (and reason why it became a warning now is that Adrian made it static), and so the code inside CONFIG_PCI is actually relying on the fact that the variable is implicitly initialized to 0. So the patch just deletes the variable. --MiKu Signed-off-by: Mika Kukkonen

[PATCH] Fix compile warning in drivers/pnp/resource.c with !CONFIG_PCI

outside this one other place (and reason why it became a warning now is that Adrian made it static), and so the code inside CONFIG_PCI is actually relying on the fact that the variable is implicitly initialized to 0. So the patch just deletes the variable. --MiKu Signed-off-by: Mika Kukkonen