From: Paulo Alcantara <pc@cjr.nz>
To: Shyam Prasad N <nspmangalore@gmail.com>,
Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH SET] fscache fixes
Date: Thu, 02 Dec 2021 17:11:24 -0300 [thread overview]
Message-ID: <87tufq7onn.fsf@cjr.nz> (raw)
In-Reply-To: <CANT5p=qfOdaFQF+EUgjgQx=zGb09FCu=zjZ7q622G--dUy7F3w@mail.gmail.com>
Hi Shyam,
Shyam Prasad N <nspmangalore@gmail.com> writes:
> Please review and consider the following fixes in fscache integration
> of cifs.ko.
>
> https://github.com/sprasad-microsoft/smb3-kernel-client/commit/d70e50047c7daa3de17c7c41a0c4ef4f9e4443c9.patch
> https://github.com/sprasad-microsoft/smb3-kernel-client/commit/089dd629653b857b6096966e9d2df301653a36ea.patch
> https://github.com/sprasad-microsoft/smb3-kernel-client/commit/a9a62cdfe26c782dadd0b94ab529b883426d0acd.patch
Thank you! BTW, this fixes the duplicated cookie warnings I noticed
while running DFS tests with fscache enabled today.
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
prev parent reply other threads:[~2021-12-02 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 12:02 [PATCH SET] fscache fixes Shyam Prasad N
2021-12-02 16:14 ` Shyam Prasad N
2021-12-02 20:11 ` Paulo Alcantara [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=87tufq7onn.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=smfrench@gmail.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