From: Qu Wenruo <wqu@suse•com>
To: dsterba@suse•cz, Stephen Rothwell <sfr@canb•auug.org.au>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
arnd@arndb•de
Subject: Re: linux-next: build warning after merge of the btrfs-kdave tree
Date: Fri, 22 Dec 2017 08:32:03 +0800 [thread overview]
Message-ID: <aac11853-d4fb-9308-8feb-b4686ca616c1@suse.com> (raw)
In-Reply-To: <20171221164936.GN3553@suse.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]
On 2017年12月22日 00:49, David Sterba wrote:
> On Wed, Dec 20, 2017 at 08:12:11AM +0800, Qu Wenruo wrote:
>> On 2017年12月20日 06:20, Stephen Rothwell wrote:
>>> After merging the btrfs-kdave tree, today's linux-next build (powerpc
>>> ppc64_defconfig) produced this warning:
>>>
>>> fs/btrfs/qgroup.c: In function 'qgroup_reserve':
>>> fs/btrfs/qgroup.c:2432:1: warning: label 'retry' defined but not used [-Wunused-label]
>>> retry:
>>> ^
>>>
>>> Introduced by commit
>>>
>>> b283738ab0ad ("Revert "btrfs: qgroups: Retry after commit on getting EDQUOT"")
>>>
>> Sorry, I forgot to clean it up.
>>
>> I'll update the patchset along with new patches to handle qgroup limit
>> better.
>
> Meanwhile I've applied the fix from Arnd to silence the warning in
> linux-next builds.
>
Some (not much, may be 2 or 3) patches is going to be updated:
btrfs: delayed-inode: Use new qgroup meta rsv for delayed inode and item
Revert "btrfs: qgroups: Retry after commit on getting EDQUOT" ( For the
lable)
And with 2 more new patches.
Do I need to resend the patchset or use separate patches for them?
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 504 bytes --]
next prev parent reply other threads:[~2017-12-22 0:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 22:20 linux-next: build warning after merge of the btrfs-kdave tree Stephen Rothwell
2017-12-20 0:12 ` Qu Wenruo
2017-12-21 16:49 ` David Sterba
2017-12-22 0:32 ` Qu Wenruo [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-03 0:21 Stephen Rothwell
2019-05-03 13:37 ` David Sterba
2019-01-23 22:53 Stephen Rothwell
2019-01-28 16:53 ` David Sterba
2018-11-26 0:06 Stephen Rothwell
2018-11-26 7:56 ` Christoph Hellwig
2017-05-17 23:41 Stephen Rothwell
2017-05-18 12:50 ` David Sterba
2017-05-25 1:31 ` Stephen Rothwell
2016-11-28 0:02 Stephen Rothwell
2016-12-06 22:38 ` Stephen Rothwell
2016-12-14 15:19 ` David Sterba
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=aac11853-d4fb-9308-8feb-b4686ca616c1@suse.com \
--to=wqu@suse$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=dsterba@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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