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, 20 Feb 2024 19:02:52 +0100 [thread overview]
Message-ID: <2024022041-vantage-ranking-2a62@gregkh> (raw)
In-Reply-To: <pkearorf3vty5zqui6souxaesd57e4oef2ds45da7sb4mfqij3@5l3r6f7uwgwe>
On Tue, Feb 20, 2024 at 12:25:25PM -0500, Kent Overstreet wrote:
> On Tue, Feb 20, 2024 at 03:34:52PM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Feb 14, 2024 at 07:51:01AM +0100, Greg Kroah-Hartman wrote:
> > > On Tue, Feb 13, 2024 at 09:28:37PM -0500, Kent Overstreet wrote:
> > > > On Tue, Feb 13, 2024 at 03:44:25PM +0100, Greg Kroah-Hartman wrote:
> > > > > 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?
> > > >
> > > > New pull request work?
> > > >
> > > > 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-6.7-stable-2024-02-13
> > >
> > > Thanks, I'll look at these after this round of -rc kernels are released,
> > > which should have most of these in the release alraedy, but not all.
> >
> > Didn't work, can you rebase on 6.7.5 please? I tried to rebase the tree
> > here, but it gave me rejects that I didn't know how to resolve.
>
> Because sasha cherry picked some of those fixes himself, despite an
> explicit ack that he wouldn't.
No, I rebased on a "clean" 6.7.5 that had no changes on top of it at
all. It had nothing to do with anything in the queue right now.
> And one of the fixes had a locking bug, and he missed the fix for that.
>
> You're going to have to revert all that if you want my pull request to
> apply.
I'll go drop those, sorry for them getting added, but again, this had
nothing to do with your pull request failing.
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-20 18:02 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
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 [this message]
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=2024022041-vantage-ranking-2a62@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