From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs stable updates for v6.7
Date: Tue, 13 Feb 2024 15:44:25 +0100 [thread overview]
Message-ID: <2024021300-deck-duffel-5d2b@gregkh> (raw)
In-Reply-To: <2024021307-reactive-woven-8543@gregkh>
On Tue, Feb 13, 2024 at 03:38:10PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Feb 08, 2024 at 08:14:39PM -0500, Kent Overstreet wrote:
> > Hi Greg, few stable updates for you -
> >
> > Cheers,
> > Kent
> >
> > The following changes since commit 0dd3ee31125508cd67f7e7172247f05b7fd1753a:
> >
> > Linux 6.7 (2024-01-07 12:18:38 -0800)
> >
> > are available in the Git repository at:
> >
> > https://evilpiepirate.org/git/bcachefs.git tags/bcachefs-for-v6.7-stable-20240208
> >
> > for you to fetch changes up to f1582f4774ac7c30c5460a8c7a6e5a82b9ce5a6a:
> >
> > bcachefs: time_stats: Check for last_event == 0 when updating freq stats (2024-02-08 15:33:11 -0500)
>
> This didn't work well :(
>
> All of the original git commit ids are gone, and for me to look them up
> and add them back by hand is a pain. I'll do it this time, but next
> time can you please include them in the commit somewhere (cherry-pick -x
> will do it automatically for you)
>
> Let's see if I can figure it out...
I got all but 3 applied, can you please send an updated set of 3 patches
for the ones I couldn't just cherry-pick from Linus's tree?
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-13 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 1:14 [GIT PULL] bcachefs stable updates for v6.7 Kent Overstreet
2024-02-13 14:38 ` Greg Kroah-Hartman
2024-02-13 14:44 ` Greg Kroah-Hartman [this message]
2024-02-14 2:28 ` Kent Overstreet
2024-02-14 6:51 ` Greg Kroah-Hartman
2024-02-20 14:34 ` Greg Kroah-Hartman
2024-02-20 17:25 ` Kent Overstreet
2024-02-20 18:02 ` Greg Kroah-Hartman
2024-02-14 2:16 ` Kent Overstreet
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=2024021300-deck-duffel-5d2b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@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