All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: sashal@kernel.org, stable@vger.kernel.org,
	stable-commits@vger.kernel.org,
	Richard Weinberger <richard@nod.at>,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Patch "hostfs: convert hostfs to use the new mount API" has been added to the 6.6-stable tree
Date: Fri, 7 Feb 2025 16:10:59 +0100	[thread overview]
Message-ID: <2025020730-divisive-zap-2416@gregkh> (raw)
In-Reply-To: <273cccc0-bbb1-4377-9ae6-a9c54ed64527@huawei.com>

On Fri, Feb 07, 2025 at 09:22:34AM +0800, Hongbo Li wrote:
> 
> 
> On 2025/2/6 11:54, Greg KH wrote:
> > On Thu, Feb 06, 2025 at 09:09:17AM +0800, Hongbo Li wrote:
> > > Well, by the way, is the patch added because there are use cases for the new
> > > mount API in hostfs?
> > 
> > I am sorry, I don't understand the question.
> > 
> 
> Sorry for my poor expression, I just wonder why this patch should be
> backported to the 6.6-stable tree. :)

Ah.  It was a dependency for a patch later in the series, and was
documented as such with the "Stable-dep-of:" line in the commit.

thanks,

greg k-h

      reply	other threads:[~2025-02-07 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250203162734.2179532-1-sashal@kernel.org>
2025-02-05  1:13 ` Patch "hostfs: convert hostfs to use the new mount API" has been added to the 6.6-stable tree Hongbo Li
2025-02-05  8:53   ` Greg KH
2025-02-06  1:09     ` Hongbo Li
2025-02-06  3:54       ` Greg KH
2025-02-07  1:22         ` Hongbo Li
2025-02-07 15:10           ` Greg KH [this message]

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=2025020730-divisive-zap-2416@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=johannes@sipsolutions.net \
    --cc=lihongbo22@huawei.com \
    --cc=richard@nod.at \
    --cc=sashal@kernel.org \
    --cc=stable-commits@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 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.