From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp"
<Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp>
Cc: "Mori.Takahiro@ab.MitsubishiElectric.co.jp"
<Mori.Takahiro@ab.MitsubishiElectric.co.jp>,
"Motai.Hirotaka@aj.MitsubishiElectric.co.jp"
<Motai.Hirotaka@aj.MitsubishiElectric.co.jp>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: exfat: remove symlink feature : Additional patch
Date: Thu, 27 Feb 2020 00:53:30 -0500 [thread overview]
Message-ID: <59586.1582782810@turing-police> (raw)
In-Reply-To: <TY1PR01MB1578C8F3D1A9F130C5844C6890EB0@TY1PR01MB1578.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
On Thu, 27 Feb 2020 02:14:02 +0000, "Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp" said:
> Thanks for comment.
>
> > Then this should have been [PATCH v2], and the fixed version [PATCH
> > v3]
>
> 2nd patch(Additional patch) not include 1st patch(RFC PATCH).
> And the 1st patch has been merged into 'staging-next'.
> Now I can't decide.
> a) Add only version information to the 2nd patch.
> b) Merge the 1st and 2nd patches.
>
> Which is better for v3?
The first part is in-tree, so we don't re-visit it in this case. You want a
new patch that consists of *only* the second set of changes, and the changelog
for the changes for that patch.
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-02-27 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 6:37 [PATCH] staging: exfat: remove symlink feature : Additional patch Tetsuhiro Kohada
2020-02-26 7:26 ` Valdis Klētnieks
2020-02-27 2:14 ` Kohada.Tetsuhiro
2020-02-27 5:53 ` Valdis Klētnieks [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=59586.1582782810@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp \
--cc=Mori.Takahiro@ab.MitsubishiElectric.co.jp \
--cc=Motai.Hirotaka@aj.MitsubishiElectric.co.jp \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).