From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
shaggy@linux.vnet.ibm.com
Subject: Re: [PATCH] JFS: Bio cleanup: Replace missing return statements
Date: Sat, 13 Oct 2007 12:28:53 -0700 [thread overview]
Message-ID: <20071013122853.aafd3c00.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20071013191110.GA20203@havoc.gtf.org>
On Sat, 13 Oct 2007 15:11:10 -0400 Jeff Garzik wrote:
>
> From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
>
> commit 6712ecf8f648118c3363c142196418f89a510b90 removed some "return 0;"
> statements, rather than changing them to null returns.
Is my git tree mucked up? It looks to me like it was commit
e30408b2a99cb7b8bf529c7dc2328a19d71894cf that removed the return 0's.
> Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
> ---
> Dave sent this under a different cover, but just in case it was missed
> in the middle of the thread, I wanted to make sure it was not missed.
>
> fs/jfs/jfs_logmgr.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/jfs/jfs_logmgr.c b/fs/jfs/jfs_logmgr.c
> index ccfd029..15a3974 100644
> --- a/fs/jfs/jfs_logmgr.c
> +++ b/fs/jfs/jfs_logmgr.c
> @@ -2234,6 +2234,8 @@ static void lbmIODone(struct bio *bio, int error)
>
> /* wakeup I/O initiator */
> LCACHE_WAKEUP(&bp->l_ioevent);
> +
> + return;
> }
>
> /*
> @@ -2258,6 +2260,7 @@ static void lbmIODone(struct bio *bio, int error)
> if (bp->l_flag & lbmDIRECT) {
> LCACHE_WAKEUP(&bp->l_ioevent);
> LCACHE_UNLOCK(flags);
> + return;
> }
>
> tail = log->wqueue;
---
~Randy
next prev parent reply other threads:[~2007-10-13 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 19:11 Jeff Garzik
2007-10-13 19:28 ` Randy Dunlap [this message]
2007-10-14 1:46 ` Dave Kleikamp
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=20071013122853.aafd3c00.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®