From: David Sterba <dsterba@suse.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Atemu <git@atemu.net>, Luca Stefani <luca.stefani.ge1@gmail.com>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] btrfs: Don't block system suspend during fstrim
Date: Mon, 25 Nov 2024 19:08:57 +0100 [thread overview]
Message-ID: <20241125180856.GE31418@suse.cz> (raw)
In-Reply-To: <2024112033-booted-kinswoman-6cb5@gregkh>
On Wed, Nov 20, 2024 at 01:17:14PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Nov 20, 2024 at 07:41:32AM +0000, Atemu wrote:
> > Hi,
> >
> >
> > > What is the git commit id in LInus's tree you are referring to here?
> >
> > It's 69313850dce33ce8c24b38576a279421f4c60996. Apparently marked for backport to 5.15+.
>
> Please see the FAILED emails about why this was not applied, here is
> one:
> https://lore.kernel.org/r/2024101412-diaphragm-sly-ea40@gregkh
>
> Have you tested and tried this commit out in these older kernels? If
> so, can you please send a working version so that we can apply them?
The conflict was trivial, only adding the linux/freezer.h include. I've
sent an updated version that applies to 6.6.
next prev parent reply other threads:[~2024-11-25 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 20:33 [PATCH v6 0/2] btrfs: Don't block system suspend during fstrim Luca Stefani
2024-09-17 20:33 ` [PATCH v6 1/2] btrfs: Split remaining space to discard in chunks Luca Stefani
2024-09-17 20:33 ` [PATCH v6 2/2] btrfs: Don't block system suspend during fstrim Luca Stefani
2024-11-19 7:54 ` git
2024-11-19 13:13 ` Greg Kroah-Hartman
2024-11-20 7:41 ` Atemu
2024-11-20 12:17 ` Greg Kroah-Hartman
2024-11-25 18:08 ` David Sterba [this message]
2024-09-18 11:52 ` [PATCH v6 0/2] " David Sterba
2024-09-18 11:53 ` David Sterba
2024-09-18 21:34 ` Qu Wenruo
2024-09-19 12:55 ` 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=20241125180856.GE31418@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=git@atemu.net \
--cc=gregkh@linuxfoundation.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.stefani.ge1@gmail.com \
/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.