From: Greg KH <gregkh@linuxfoundation.org>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: stable@vger.kernel.org
Subject: Re: apply 'exfat: use updated exfat_chain directly during renaming' to 5.15.y/5.18.y please
Date: Wed, 27 Jul 2022 10:15:16 +0200 [thread overview]
Message-ID: <YuD0FJ8DcNjCIHuU@kroah.com> (raw)
In-Reply-To: <20220726063556.958C.409509F4@e16-tech.com>
On Tue, Jul 26, 2022 at 06:35:57AM +0800, Wang Yugui wrote:
> Hi,
>
> apply 'exfat: use updated exfat_chain directly during renaming' to 5.15.y/5.18.y please.
>
> because it fix some problem of the patch
> 'exfat-fix-referencing-wrong-parent-directory-informa.patch'
> just applied in to 5.15.y/5.18.y
>
> exfat: use updated exfat_chain directly during renaming
> Fixes: d8dad2588add ("exfat: fix referencing wrong parent directory information after renaming")
Now queued up.
Next time also give me a hint as to what the git commit id in Linus's
tree that I need to pick, so I don't have to dig through the changelog.
thanks,
greg k-h
prev parent reply other threads:[~2022-07-27 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 22:35 apply 'exfat: use updated exfat_chain directly during renaming' to 5.15.y/5.18.y please Wang Yugui
2022-07-27 8:15 ` 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=YuD0FJ8DcNjCIHuU@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=wangyugui@e16-tech.com \
/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