All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: 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: Wed, 5 Feb 2025 09:53:05 +0100	[thread overview]
Message-ID: <2025020534-family-upgrade-20fb@gregkh> (raw)
In-Reply-To: <e71dbfcd-317e-43b0-8e67-2a7ea3510281@huawei.com>

On Wed, Feb 05, 2025 at 09:13:33AM +0800, Hongbo Li wrote:
> 
> 
> On 2025/2/4 0:27, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> > 
> >      hostfs: convert hostfs to use the new mount API
> > 
> > to the 6.6-stable tree which can be found at:
> >      http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> 
> Hi Sasha,
> 
> If this, the fix : ef9ca17ca458 ("hostfs: fix the host directory parse when
> mounting.") also should be added. It fixes the mounting bug when pass the
> host directory.

I've swept the queues and have added the "fixes for the fixes" commits
like this one now, thanks!

greg k-h

  reply	other threads:[~2025-02-05  8:53 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 [this message]
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

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=2025020534-family-upgrade-20fb@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=johannes@sipsolutions.net \
    --cc=lihongbo22@huawei.com \
    --cc=richard@nod.at \
    --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.