From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.com>
Cc: torvalds@linux-foundation.org, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 6.17
Date: Tue, 29 Jul 2025 09:55:57 +1000 [thread overview]
Message-ID: <20250729095557.30be0750@canb.auug.org.au> (raw)
In-Reply-To: <cover.1753226358.git.dsterba@suse.com>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Hi David,
On Wed, 23 Jul 2025 01:23:47 +0200 David Sterba <dsterba@suse.com> wrote:
>
> Hi,
>
> there's are number of usability and feature updates, scattered
> performance improvements and fixes. Highlight of the core changes is
> getting closer to enabling large folios (now behind a config option).
It looks like this was all rebased from what is in linux-next :-(
Please clean up the btrfs trees in linux-next.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-28 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 23:23 David Sterba
2025-07-28 23:40 ` pr-tracker-bot
2025-07-28 23:55 ` Stephen Rothwell [this message]
2025-08-04 9:40 ` 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=20250729095557.30be0750@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®