public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the btrfs-fixes tree
Date: Tue, 3 Feb 2026 08:47:51 +0100	[thread overview]
Message-ID: <20260203074751.GM26902@suse.cz> (raw)
In-Reply-To: <541681ab-07f7-49ce-bb74-c3e52b71b659@sirena.org.uk>

On Mon, Feb 02, 2026 at 02:57:25PM +0000, Mark Brown wrote:
> On Thu, Jan 29, 2026 at 12:51:15PM +0000, Mark Brown wrote:
> > Hi all,
> > 
> > After merging the btrfs-fixes tree, today's linux-next build
> > (arm64 defconfig) failed like this:
> 
> This issue is still present in today's -next.

I forgot to push the fixed branch, should be fixed in today's snapshot.
Thanks.

  reply	other threads:[~2026-02-03  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 12:51 linux-next: build failure after merge of the btrfs-fixes tree Mark Brown
2026-02-02 14:57 ` Mark Brown
2026-02-03  7:47   ` David Sterba [this message]
  -- 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
2024-03-17 22:17 Stephen Rothwell
2024-03-18  4:50 ` Anand Jain
2024-03-18 17:31 ` David Sterba
2024-03-18 18:58 ` David Sterba
     [not found] <20200107082431.2b83a8ac@canb.auug.org.au>
2020-01-07 15:22 ` 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=20260203074751.GM26902@suse.cz \
    --to=dsterba@suse.cz \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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