From: Markus Elfring <Markus.Elfring@web.de>
To: Namjae Jeon <namjae.jeon@samsung.com>, linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>,
"Christoph Hellwig" <hch@lst.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Sungjong Seo" <sj1557.seo@samsung.com>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
linkinjeon@gmail.com
Subject: Re: [PATCH v10 00/14] add the latest exfat driver
Date: Thu, 16 Jan 2020 10:36:36 +0100 [thread overview]
Message-ID: <7e5e56be-5b87-8f9c-60fa-134a13f8e762@web.de> (raw)
> We plan to treat this version as the future upstream for the code base
> once merged, and all new features and bug fixes will go upstream first.
>
> v10:
I find it interesting how the patch change log grew.
> - Process length value as 1 when conversion is failed.
Would this description be nicer without the word “is”?
I pointed also further software development concerns out.
I hope that they will get corresponding constructive feedback finally.
Other contributors are similarly waiting for “effects” according to
their code review comments.
How will communication delays evolve for the clarification of
remaining open issues?
Regards,
Markus
next reply other threads:[~2020-01-16 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 9:36 Markus Elfring [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-16 14:45 [PATCH v10 00/14] add the latest exfat driver Markus Elfring
[not found] <CGME20200115082818epcas1p4892a99345626188afd111ee263132458@epcas1p4.samsung.com>
2020-01-15 8:24 ` Namjae Jeon
2020-01-15 9:47 ` Pali Rohár
2020-01-15 13:05 ` Namjae Jeon
2020-01-16 10:51 ` Christoph Hellwig
2020-01-16 11:32 ` Pali Rohár
2020-01-16 13:01 ` Greg KH
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=7e5e56be-5b87-8f9c-60fa-134a13f8e762@web.de \
--to=markus.elfring@web.de \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=pali.rohar@gmail.com \
--cc=sj1557.seo@samsung.com \
--cc=valdis.kletnieks@vt.edu \
/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).