public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: one 'BUG_ON(ret < 0);' is still left in queue-6.1/btrfs-do-not-bug_on-on-tree-mod-log-failure-at-balan.patch
Date: Sun, 16 Jul 2023 17:47:03 +0800	[thread overview]
Message-ID: <20230716174658.DC0B.409509F4@e16-tech.com> (raw)
In-Reply-To: <2023071634-cogwheel-handgun-7cdb@gregkh>

Hi,

> On Sat, Jul 15, 2023 at 07:02:27AM +0800, Wang Yugui wrote:
> > Hi,
> > 
> > one 'BUG_ON(ret < 0);' is still left in queue-6.1/btrfs-do-not-bug_on-on-tree-mod-log-failure-at-balan.patch 
> > 
> > so we need to rebase this patch.
> 
> Great, can you send a new version for 5.15.y and 6.1.y?

queue-5.15/btrfs-do-not-bug_on-on-tree-mod-log-failure-at-balan.patch is GOOD.
queue-6.1/btrfs-do-not-bug_on-on-tree-mod-log-failure-at-balan.patch is GOOD.

and we can 'git am' queue-5.15/btrfs-do-not-bug_on-on-tree-mod-log-failure-at-balan.patch
to 6.1.38 cleanly.

so it is OK to just copy queue-5.15/btrfs-do-not-bug_on-on-tree-mod-log-failure-at-balan.patch
as queue-6.1/btrfs-do-not-bug_on-on-tree-mod-log-failure-at-balan.patch.

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/07/16


  reply	other threads:[~2023-07-16  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 23:02 one 'BUG_ON(ret < 0);' is still left in queue-6.1/btrfs-do-not-bug_on-on-tree-mod-log-failure-at-balan.patch Wang Yugui
2023-07-16  9:24 ` Greg KH
2023-07-16  9:47   ` Wang Yugui [this message]
2023-07-16 15:12     ` Greg KH

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=20230716174658.DC0B.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=gregkh@linuxfoundation.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