From: Paulo Alcantara <pc@cjr.nz>
To: Enzo Matsumiya <ematsumiya@suse.de>, linux-cifs@vger.kernel.org
Cc: smfrench@gmail.com, ronniesahlberg@gmail.com,
nspmangalore@gmail.com, Enzo Matsumiya <ematsumiya@suse.de>
Subject: Re: [PATCH] cifs: print TIDs as hex
Date: Wed, 18 May 2022 13:22:05 -0300 [thread overview]
Message-ID: <87a6be3j6a.fsf@cjr.nz> (raw)
In-Reply-To: <20220518144105.21913-2-ematsumiya@suse.de>
Enzo Matsumiya <ematsumiya@suse.de> writes:
> Signed-off-by: Enzo Matsumiya <ematsumiya@suse.de>
> ---
> fs/cifs/connect.c | 2 +-
> fs/cifs/smb2misc.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
next prev parent reply other threads:[~2022-05-18 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:41 [PATCH] cifs: don't call cifs_dfs_query_info_nonascii_quirk() if nodfs was set Enzo Matsumiya
2022-05-18 14:41 ` [PATCH] cifs: print TIDs as hex Enzo Matsumiya
2022-05-18 16:22 ` Paulo Alcantara [this message]
2022-05-18 14:41 ` [PATCH] cifs: return ENOENT for DFS lookup_cache_entry() Enzo Matsumiya
2022-05-18 16:23 ` Paulo Alcantara
2022-05-18 16:20 ` [PATCH] cifs: don't call cifs_dfs_query_info_nonascii_quirk() if nodfs was set Paulo Alcantara
2022-05-18 16:24 ` Enzo Matsumiya
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=87a6be3j6a.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=ematsumiya@suse.de \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=ronniesahlberg@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 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.