From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.15 stable
Date: Sat, 7 Jun 2025 10:36:31 +0200 [thread overview]
Message-ID: <2025060721-retaining-thursday-471c@gregkh> (raw)
In-Reply-To: <xlnudv42ksgzhydnz4uefmiuh4f6ebtixwwjh2mwj5fivw24ll@tczlx6fmsu5k>
On Thu, Jun 05, 2025 at 03:31:14PM -0400, Kent Overstreet wrote:
> The following changes since commit 3ef49626da6dd67013fc2cf0a4e4c9e158bb59f7:
>
> Linux 6.15.1 (2025-06-04 14:46:27 +0200)
>
> are available in the Git repository at:
>
> git://evilpiepirate.org/bcachefs.git tags/bcachefs-for-6.15-2025-06-05
>
> for you to fetch changes up to fc9459c9a888766c4c4adff59b072aad1bfbf6ad:
>
> bcachefs: Fix subvol to missing root repair (2025-06-05 14:04:58 -0400)
Now queued up, thanks!
greg k-h
prev parent reply other threads:[~2025-06-07 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 19:31 [GIT PULL] bcachefs fixes for 6.15 stable Kent Overstreet
2025-06-07 8:36 ` Greg Kroah-Hartman [this message]
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=2025060721-retaining-thursday-471c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).