From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josef@suse.de
Subject: Re: linux-next: build failure after merge of the btrfs-fixes tree
Date: Tue, 7 Jan 2020 16:22:04 +0100 [thread overview]
Message-ID: <20200107152204.GX3929@suse.cz> (raw)
In-Reply-To: <20200107082431.2b83a8ac@canb.auug.org.au>
On Tue, Jan 07, 2020 at 08:24:31AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the btrfs-fixes tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> fs/btrfs/inode.c: In function 'btrfs_unlink_subvol':
> fs/btrfs/inode.c:4283:16: error: 'inode' undeclared (first use in this function)
> 4283 | if (btrfs_ino(inode) == BTRFS_EMPTY_SUBVOL_DIR_OBJECTID) {
> | ^~~~~
>
> Caused by commit
>
> b225d1cb20cc ("btrfs: fix invalid removal of root ref")
>
> I have reverted that commit for today.
Updated next-fixes branch pushed.
next parent reply other threads:[~2020-01-07 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200107082431.2b83a8ac@canb.auug.org.au>
2020-01-07 15:22 ` David Sterba [this message]
2024-03-17 22:17 linux-next: build failure after merge of the btrfs-fixes tree Stephen Rothwell
2024-03-18 4:50 ` Anand Jain
2024-03-18 17:31 ` David Sterba
2024-03-18 18:58 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2026-01-20 12:07 Mark Brown
2026-01-20 12:22 ` Johannes Thumshirn
2026-01-20 12:32 ` Mark Brown
2026-01-20 16:18 ` David Sterba
2026-01-20 23:33 ` Qu Wenruo
2026-01-29 12:51 Mark Brown
2026-02-02 14:57 ` Mark Brown
2026-02-03 7:47 ` 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=20200107152204.GX3929@suse.cz \
--to=dsterba@suse.cz \
--cc=Josef@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.