From: Vasant Karasulli <vkarasulli@suse.de>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: David Disseldorp <ddiss@suse.de>,
Sungjong Seo <sj1557.seo@samsung.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
Kohada.Tetsuhiro@dc.mitsubishielectric.co.jp
Subject: Re: [PATCH v3 1/2] exfat: add keep_last_dots mount option
Date: Wed, 16 Mar 2022 15:44:05 +0100 [thread overview]
Message-ID: <YjH3tcLbJTTxDwPY@vasant-suse> (raw)
In-Reply-To: <CAKYAXd-EhGuywjtH8T4aFRJ6sP4nGvS=5O2u+EULLV+8s=0T4A@mail.gmail.com>
On Mi 16-03-22 23:08:32, Namjae Jeon wrote:
> 2022-03-16 22:57 GMT+09:00, David Disseldorp <ddiss@suse.de>:
> > On Wed, 16 Mar 2022 10:20:28 +0100, Vasant Karasulli wrote:
> >
> >> On So 13-03-22 09:01:32, Namjae Jeon wrote:
> >> > 2022-03-11 20:47 GMT+09:00, Vasant Karasulli <vkarasulli@suse.de>:
> >> > > The "keep_last_dots" mount option will, in a
> >> > > subsequent commit, control whether or not trailing periods '.' are
> >> > > stripped
> >> > > from path components during file lookup or file creation.
> >> > I don't know why the 1/2 patch should be split from the 2/2 patch.
> >> > Wouldn't it be better to combine them? Otherwise it looks good to me.
> >>
> >> I just followed the same patch structure as was in the initial version
> >> of the patch.
> >
> > I'm fine with having both patches squashed together. @Namjae: should we
> > resubmit as a single patch or can you do the squash on your side before
> > submitting to Linus?
> I would be grateful if you resubmit it to the list after making it one:)
>
Ok, I will resubmit as a single patch in the new version of the patch.
Thanks,
Vasant Karasulli
Kernel generalist
www.suse.com<http://www.suse.com>
[https://www.suse.com/assets/img/social-platforms-suse-logo.png]<http://www.suse.com/>
SUSE - Open Source Solutions for Enterprise Servers & Cloud<http://www.suse.com/>
Modernize your infrastructure with SUSE Linux Enterprise servers, cloud technology for IaaS, and SUSE's software-defined storage.
www.suse.com
next prev parent reply other threads:[~2022-03-16 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 11:47 [PATCH v3 0/2] exfat: allow access to paths with trailing dots Vasant Karasulli
2022-03-11 11:47 ` [PATCH v3 1/2] exfat: add keep_last_dots mount option Vasant Karasulli
2022-03-13 0:01 ` Namjae Jeon
2022-03-16 9:20 ` Vasant Karasulli
2022-03-16 13:57 ` David Disseldorp
2022-03-16 14:08 ` Namjae Jeon
2022-03-16 14:44 ` Vasant Karasulli [this message]
2022-03-11 11:47 ` [PATCH v3 2/2] exfat: keep trailing dots in paths if keep_last_dots is Vasant Karasulli
2022-03-16 18:06 ` David Disseldorp
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=YjH3tcLbJTTxDwPY@vasant-suse \
--to=vkarasulli@suse.de \
--cc=Kohada.Tetsuhiro@dc.mitsubishielectric.co.jp \
--cc=ddiss@suse.de \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).