From: "Tiezhu Yang" <kernelpatch@126.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re:Re: [f2fs-dev] [PATCH] f2fs: return proper error code
Date: Wed, 13 Jul 2016 08:27:54 +0800 (CST) [thread overview]
Message-ID: <6e9a1184.c02.155e1a720cd.Coremail.kernelpatch@126.com> (raw)
In-Reply-To: <a4172278-7eca-1841-89b2-fddd72a92ba8@huawei.com>
At 2016-07-12 09:45:43, "Chao Yu" <yuchao0@huawei.com> wrote:
>On 2016/7/11 7:20, Tiezhu Yang wrote:
>> When the length of file name is more than F2FS_NAME_LEN,
>
>Seem @name indicates a xattr/key name, not a file name.
Yes, you are right. Sorry for the noise.
Thanks,
prev parent reply other threads:[~2016-07-13 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 23:20 [PATCH] f2fs: return proper error code Tiezhu Yang
2016-07-12 1:45 ` Chao Yu
2016-07-13 0:27 ` Tiezhu Yang [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=6e9a1184.c02.155e1a720cd.Coremail.kernelpatch@126.com \
--to=kernelpatch@126.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@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 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).