From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] Btrfs: fix range cloning when same inode used as source and destination
Date: Thu, 2 Apr 2015 17:31:42 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.04.02.17.31.42@googlemail.com> (raw)
In-Reply-To: 1427995511-13028-1-git-send-email-fdmanana@suse.com
On Thu, 02 Apr 2015 18:25:11 +0100, Filipe Manana wrote:
> V2: Fixed a warning about potentially uninitialized variable. David
> got this warning on a 4.5.1 gcc, but I didn't on a 4.9.2 gcc
> however.
I was *just* about to post this warning, since I saw it only a minute ago!
I assume you mean:
fs/btrfs/ioctl.c: In function 'btrfs_clone':
fs/btrfs/ioctl.c:3531:14: warning: 'next_key_min_offset' may be used uninitialized in this function [-Wmaybe-uninitialized]
key.offset = next_key_min_offset;
^
..and this is with 4.9.2 here.
Anyway..thanks for being faster :)
Holger
next prev parent reply other threads:[~2015-04-02 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 13:56 [PATCH] Btrfs: fix range cloning when same inode used as source and destination Filipe Manana
2015-04-02 17:25 ` [PATCH v2] " Filipe Manana
2015-04-02 17:31 ` Holger Hoffstätte [this message]
2015-04-02 18:03 ` Filipe David Manana
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=pan.2015.04.02.17.31.42@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@vger.kernel.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).