From: Alex Elder <aelder@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix unused variable warning
Date: Thu, 6 Oct 2011 06:24:27 -0500 [thread overview]
Message-ID: <1317900267.3139.9.camel@doink> (raw)
In-Reply-To: <1317877059-7024-1-git-send-email-david@fromorbit.com>
On Thu, 2011-10-06 at 15:57 +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Fix this warning:
>
> fs/xfs/xfs_aops.c: In function 'xfs_end_io_direct_write':
> fs/xfs/xfs_aops.c:1280:17: warning: unused variable 'inode' [-Wunused-variable]
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
That line of code is not present in the current XFS
master branch on oss.sgi.com.
-Alex
> ---
> fs/xfs/xfs_aops.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index 462e937..11b2aad 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_aops.c
> @@ -1277,7 +1277,6 @@ xfs_end_io_direct_write(
> bool is_async)
> {
> struct xfs_ioend *ioend = iocb->private;
> - struct inode *inode = ioend->io_inode;
>
> /*
> * blockdev_direct_IO can return an error even after the I/O
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-06 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 4:57 [PATCH] xfs: fix unused variable warning Dave Chinner
2011-10-06 11:24 ` Alex Elder [this message]
2011-10-06 21:56 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2021-02-04 16:03 Arnd Bergmann
2021-02-04 18:07 ` Brian Foster
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=1317900267.3139.9.camel@doink \
--to=aelder@sgi.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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