The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Baokun Li <libaokun@linux.alibaba.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Jiayuan Chen <jiayuan.chen@linux.dev>,
	Wang Jun <1742789905@qq.com>,
	adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	25125332@bjtu.edu.cn, Jan Kara <jack@suse.cz>,
	Ojaswin Mujoo <ojaswin@linux.ibm.com>
Subject: Re: [PATCH] ext4: get rid of ppath in get_ext_path()
Date: Fri, 3 Jul 2026 07:48:08 -0400	[thread overview]
Message-ID: <akehR1wEgK23wFp4@mit.edu> (raw)
In-Reply-To: <2904d1db-11fa-450a-89ea-20fe133fa268@linux.alibaba.com>

On Fri, Jul 03, 2026 at 04:44:32PM -0500, Baokun Li wrote:
> >> Either applying this fix patchset or reverting the incorrectly merged
> >> commit should resolve the issue.
> > How about submitting a revert so that we can start fresh and work from
> > there?
> 
> Alright, I can help review the patches.

Can you also double check whether your patchset actually fixes a bug
in 6.6?  As near as I can tell, it wasn't needed for 6.1 at all.

Thanks,

						- Ted

  reply	other threads:[~2026-07-03 11:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  5:17 [PATCH] ext4: get rid of ppath in get_ext_path() Wang Jun
2026-06-26  6:49 ` Greg KH
2026-06-26  7:08   ` [PATCH] ext4: fix crash when ext4_ext_insert_extent() returns error Wang Jun
2026-07-02  1:48   ` [PATCH] ext4: get rid of ppath in get_ext_path() Jiayuan Chen
2026-07-02  5:47     ` Greg KH
2026-07-02  6:09       ` Jiayuan Chen
2026-07-02 18:20         ` Theodore Tso
2026-07-03  7:57       ` Baokun Li
2026-07-03  8:20         ` Greg KH
2026-07-03  8:44           ` Baokun Li
2026-07-03 11:48             ` Theodore Tso [this message]
2026-07-04  2:04           ` Sasha Levin
2026-07-02 14: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=akehR1wEgK23wFp4@mit.edu \
    --to=tytso@mit.edu \
    --cc=1742789905@qq.com \
    --cc=25125332@bjtu.edu.cn \
    --cc=adilger.kernel@dilger.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=jiayuan.chen@linux.dev \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.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