All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Heming Zhao <heming.zhao@suse.com>
Cc: joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, ocfs2-devel@lists.linux.dev
Subject: Re: [PATCH] ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"
Date: Thu, 12 Dec 2024 13:28:43 +0100	[thread overview]
Message-ID: <2024121222-smoked-gossip-d970@gregkh> (raw)
In-Reply-To: <92d413be-286e-49b7-a234-b6e2c8c94581@suse.com>

On Thu, Dec 12, 2024 at 07:45:11PM +0800, Heming Zhao wrote:
> Hi Greg,
> 
> The 4.19 branch also needs this patch.

4.19.y is end-of-life, sorry (see the front page of kernel.org for the
current list.)

thanks,

greg k-h

  reply	other threads:[~2024-12-12 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 11:31 [PATCH] ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume" Heming Zhao
2024-12-12 11:40 ` Patch "ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"" has been added to the 5.4-stable tree gregkh
2024-12-12 11:40 ` Patch "ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"" has been added to the 5.10-stable tree gregkh
2024-12-12 11:40 ` Patch "ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"" has been added to the 5.15-stable tree gregkh
2024-12-12 11:40 ` Patch "ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"" has been added to the 6.1-stable tree gregkh
2024-12-12 11:40 ` Patch "ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"" has been added to the 6.6-stable tree gregkh
2024-12-12 11:45 ` [PATCH] ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume" Heming Zhao
2024-12-12 12:28   ` Greg KH [this message]
2024-12-12 11:47 ` Patch "ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume"" has been added to the 6.12-stable tree gregkh

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=2024121222-smoked-gossip-d970@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=heming.zhao@suse.com \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.