From: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong1@huawei.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH V3 2/2] mkfs.f2fs: skip extension name that is too long
Date: Tue, 1 Dec 2015 22:20:14 +0800 [thread overview]
Message-ID: <565DAC9E.4080303@kernel.org> (raw)
In-Reply-To: <565BBB40.3010206@huawei.com>
Hi Sheng,
On 11/30/15 10:58 AM, Sheng Yong wrote:
> Hi, Chao Yu, Jaegeuk
>
> I'm not sure if it is ok to send this patch out by me. If I did it the
> wrong way, please ignore this patch.
It's OK to me, thanks for your reediting. :)
Regards,
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
prev parent reply other threads:[~2015-12-01 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 10:41 [PATCH V3 1/2] mkfs.f2fs: avoid dumplicate extensions Sheng Yong
2015-11-30 10:41 ` [PATCH V3 2/2] mkfs.f2fs: skip extension name that is too long Sheng Yong
2015-11-30 2:58 ` Sheng Yong
2015-12-01 14:20 ` Chao Yu [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=565DAC9E.4080303@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=shengyong1@huawei.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.