mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Alex Romosan <aromosan@gmail.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	Anand Jain <anand.jain@oracle.com>,
	CHECK_1234543212345@protonmail.com, brauner@kernel.org,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Chris Mason <clm@fb.com>,
	Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>,
	dsterba@suse.cz
Subject: Re: [btrfs] commit bc27d6f0aa0e4de184b617aceeaf25818cc646de breaks update-grub
Date: Mon, 5 Feb 2024 12:26:19 +0100	[thread overview]
Message-ID: <20240205112619.GC355@twin.jikos.cz> (raw)
In-Reply-To: <CAKLYgeKCuDmnuGHuQYPdZZA1_H3s9_9oh+vT_FMpFZqxKSvjzw@mail.gmail.com>

On Sun, Feb 04, 2024 at 07:29:29PM +0100, Alex Romosan wrote:
> sorry about the html post (in case somebody actually got it). as i was
> saying, just for the record it's still not fixed in 6.8-rc3. thanks.

I've updated the bug with link to fix

https://github.com/kdave/btrfs-devel/commit/b80f3ec6592c69f88ebc74a4e16676af161e2759

but would like to ask for testing.

  reply	other threads:[~2024-02-05 11:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 14:11 Alex Romosan
2024-01-11 11:45 ` Thorsten Leemhuis
2024-01-11 15:50   ` David Sterba
2024-01-11 17:06     ` David Sterba
2024-01-11 23:24       ` Anand Jain
2024-01-22  0:07         ` Alex Romosan
2024-01-22  1:35           ` Anand Jain
2024-01-22  1:46             ` Alex Romosan
2024-02-01 10:25         ` Linux regression tracking (Thorsten Leemhuis)
2024-02-03 22:03           ` David Sterba
     [not found]           ` <CAKLYgeLhcE5+Td9eGKAi0xeXSsom381RxuJgKiQ0+oHDNS_DJA@mail.gmail.com>
2024-02-04 18:29             ` Alex Romosan
2024-02-05 11:26               ` David Sterba [this message]
2024-02-05 12:38                 ` Alex Romosan

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=20240205112619.GC355@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=CHECK_1234543212345@protonmail.com \
    --cc=anand.jain@oracle.com \
    --cc=aromosan@gmail.com \
    --cc=brauner@kernel.org \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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
all inboxes | Powered by JetHome®