From: "Pali Rohár" <pali@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: Steve French <sfrench@samba.org>,
Paulo Alcantara <pc@manguebit.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: Add support for parsing WSL-style symlinks
Date: Mon, 25 Nov 2024 23:25:17 +0100 [thread overview]
Message-ID: <20241125222517.wxtwgfjs5rkcr7pj@pali> (raw)
In-Reply-To: <CAH2r5mtLoAsZfHHe33=WfDjLZ1PNgV-SgcN1F-o0g1XXLsoAng@mail.gmail.com>
On Monday 25 November 2024 15:24:03 Steve French wrote:
> This patch
>
> commit 06a7adf318a30bdcfa1222ed6d2640e6bb266d7b
> Author: Pali Rohár <pali@kernel.org>
> Date: Sat Sep 28 13:21:24 2024 +0200
>
> cifs: Add support for parsing WSL-style symlinks
>
>
> led to compile warning:
>
> CC [M] fs/smb/client/reparse.o
> CHECK fs/smb/client/reparse.c
> fs/smb/client/reparse.c:679:45: warning: incorrect type in argument 4
> (different base types)
> fs/smb/client/reparse.c:679:45: expected unsigned short [usertype] *pwcs
> fs/smb/client/reparse.c:679:45: got restricted __le16 [usertype]
> *[assigned] symname_utf16
>
>
> Let me know if updated version needed
I have already reacted for this problem more than month ago:
https://lore.kernel.org/oe-kbuild-all/20241007213401.bsfqwlb4c2k6ynlr@pali/
But nobody on the list replied :-( So I do not know what is the best way
to handle this issue.
prev parent reply other threads:[~2024-11-25 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 9:05 [PATCH] cifs: Add support for parsing WSL-style symlinks Pali Rohár
[not found] ` <202410080458.o4vvmJkR-lkp@intel.com>
2024-10-07 21:34 ` Pali Rohár
2024-11-25 21:24 ` Steve French
2024-11-25 22:25 ` Pali Rohár [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=20241125222517.wxtwgfjs5rkcr7pj@pali \
--to=pali@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.org \
--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