From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: paulus@samba.org
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH] [POWERPC] Invalid semicolon after if statement
Date: Thu, 16 Aug 2007 01:03:35 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708151644090.15670@kivilampi-30.cs.helsinki.fi> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1030 bytes --]
A similar fix to netfilter from Eric Dumazet inspired me to
look around a bit by using some grep/sed stuff as looking for
this kind of bugs seemed easy to automate. This is one of them
I found where it looks like this semicolon is not valid.
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
---
...Since I'm not familiar with these parts of the kernel, you might know
better than I do if this is stuff is valid...
arch/powerpc/mm/hash_utils_64.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/mm/hash_utils_64.c b/arch/powerpc/mm/hash_utils_64.c
index f178957..a47151e 100644
--- a/arch/powerpc/mm/hash_utils_64.c
+++ b/arch/powerpc/mm/hash_utils_64.c
@@ -795,7 +795,7 @@ void hash_preload(struct mm_struct *mm, unsigned long ea,
#ifdef CONFIG_PPC_MM_SLICES
/* We only prefault standard pages for now */
- if (unlikely(get_slice_psize(mm, ea) != mm->context.user_psize));
+ if (unlikely(get_slice_psize(mm, ea) != mm->context.user_psize))
return;
#endif
--
1.5.0.6
next reply other threads:[~2007-08-15 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 22:03 Ilpo Järvinen [this message]
2007-08-16 7:22 ` [PATCH] [POWERPC] Invalid semicolon after if statement Geert Uytterhoeven
2007-08-16 8:08 ` Michael Ellerman
2007-08-16 14:03 ` Segher Boessenkool
2007-08-16 16:40 ` Andreas Schwab
2007-08-16 23:08 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0708151644090.15670@kivilampi-30.cs.helsinki.fi \
--to=ilpo.jarvinen@helsinki.fi \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).