stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Joseph Qi <jiangqi903@gmail.com>,
	gregkh@linuxfoundation.org, ocfs2-devel@oss.oracle.com,
	akpm@linux-foundation.org, gechangwei@live.cn, ghe@suse.com,
	jack@suse.cz, jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
	junxiao.bi@oracle.com, mark@fasheh.com, piaojun@huawei.com,
	stable@vger.kernel.org
Subject: Re: [Ocfs2-devel] FAILED: patch "[PATCH] ocfs2: fix data corruption after failed write" failed to apply to 5.10-stable tree
Date: Tue, 21 Mar 2023 09:13:20 +0700	[thread overview]
Message-ID: <ZBkSwL37/9DpfnvP@debian.me> (raw)
In-Reply-To: <63069869-30cf-c45f-3b05-b0b9b46bc36a@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

On Tue, Mar 21, 2023 at 10:06:30AM +0800, Joseph Qi wrote:
> Hi Greg,
> It can be cleanly applied for linux-5.10.y and linux-4.19.y in my desktop.
> I'm not sure how it happens.
> 

If you can apply the backport, why don't you post it here?

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-03-21  2:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 11:57 FAILED: patch "[PATCH] ocfs2: fix data corruption after failed write" failed to apply to 5.10-stable tree gregkh
2023-03-21  2:06 ` [Ocfs2-devel] " Joseph Qi
2023-03-21  2:13   ` Bagas Sanjaya [this message]
2023-03-21  2:21     ` Joseph Qi
2023-03-21  3:00 ` [PATCH] ocfs2: fix data corruption after failed write Joseph Qi

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=ZBkSwL37/9DpfnvP@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gechangwei@live.cn \
    --cc=ghe@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=jiangqi903@gmail.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=junxiao.bi@oracle.com \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=piaojun@huawei.com \
    --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).