All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Steve French <sfrench@samba.org>,
	Steve French <stfrench@microsoft.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Hyunchul Lee <hyc.lee@gmail.com>,
	linux-cifs@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: No fs/cifs_common directory in kernel tree
Date: Tue, 28 Sep 2021 14:37:03 +0900	[thread overview]
Message-ID: <CAKYAXd_N5juxVTbfA0cVMMKbZa3sk1MnCeBjoMxQnmzEK4Paqw@mail.gmail.com> (raw)
In-Reply-To: <CAKXUXMyhrjf0=0jaYG89zHULKGA-z+tgUZr=tQmBWZZUCCDuwQ@mail.gmail.com>

2021-09-28 13:19 GMT+09:00, Lukas Bulwahn <lukas.bulwahn@gmail.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
>

      reply	other threads:[~2021-09-28  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28  4:19 No fs/cifs_common directory in kernel tree Lukas Bulwahn
2021-09-28  5:37 ` Namjae Jeon [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=CAKYAXd_N5juxVTbfA0cVMMKbZa3sk1MnCeBjoMxQnmzEK4Paqw@mail.gmail.com \
    --to=linkinjeon@kernel.org \
    --cc=hyc.lee@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=senozhatsky@chromium.org \
    --cc=sfrench@samba.org \
    --cc=stfrench@microsoft.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.