[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKYAXd_N5juxVTbfA0cVMMKbZa3sk1MnCeBjoMxQnmzEK4Paqw@mail.gmail.com>
Date: Tue, 28 Sep 2021 14:37:03 +0900
From: Namjae Jeon <linkinjeon@...nel.org>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: Steve French <sfrench@...ba.org>,
Steve French <stfrench@...rosoft.com>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Hyunchul Lee <hyc.lee@...il.com>, linux-cifs@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: No fs/cifs_common directory in kernel tree
2021-09-28 13:19 GMT+09:00, Lukas Bulwahn <lukas.bulwahn@...il.com>:
> Dear Steve, dear Namjae,
Hi Lukas,
First, Thanks for your report!
>
> I am tracking consistency of the MAINTAINERS file and noticed:
>
> Commit 332c404a55ef ("cifs: add cifs_common directory to MAINTAINERS
> file") and commit e9e3d5f9e34c ("MAINTAINERS: ksmbd: add cifs_common
> directory to ksmbd entry") add the file entry fs/cifs_common/ to the
> sections COMMON INTERNET FILE SYSTEM CLIENT (CIFS) and KERNEL SMB3
> SERVER (KSMBD).
>
> However, as of now, there is no fs/cifs_common/ directory in the
> mainline tree or in the latest linux-next tree.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file matches F: fs/cifs_common/
>
> Are there more commits to come that will add or move files to
> fs/cifs_common/, or did you decide against introducing fs/cifs_common/
> in the course of the development and these commits are left-over from
> a previous development?
cifs_common directory has recently been renamed to smbfs_common.
I will update cifs and ksmbd entry in MAINTAINERS.
Thanks!
>
> Best regards,
>
> Lukas
>
Powered by blists - more mailing lists