From: nick <xerofoify@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>,
Liu Song <liu.song11@zte.com.cn>
Cc: cui.yunfeng@zte.com.cn, Artem Bityutskiy <dedekind1@gmail.com>,
linux-mtd@lists.infradead.org, jiang.xuexin@zte.com.cn,
wang.bo116@zte.com.cn, dwmw2@infradead.org,
deng.chao1@zte.com.cn
Subject: Re: [PATCH]jffs2:bugfix for should not appeared directory hard link
Date: Tue, 16 Dec 2014 21:02:30 -0500 [thread overview]
Message-ID: <5490E436.7020200@gmail.com> (raw)
In-Reply-To: <20141217015338.GR9759@ld-irv-0074>
Greetings Brian,
Are you sure jffs2 is obsolete now? I seem to known of a few areas in embedded that are still using this file system unless we are moving toward f2fs for flash file systems. If that is the case why not just remove it from main line as
no one is supporting it outside legacy code for older devices and embedded systems.
Regards Nick
On 2014-12-16 08:53 PM, Brian Norris wrote:
>> > Thanks a lot for your attention and suggestions. Follow the guide, patch had checked by checkpatch.pl,
>> > but there also had warnings about line over 80 characters, I had no idea to fix that except remove the
>> > code indentations, but i'm afraid that would make codes hard to read. However, if there are any
>> > suggestions to fix this I would try.
> Sometimes you can break a line in the middle, where necessar
next prev parent reply other threads:[~2014-12-17 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 9:26 [PATCH]jffs2:bugfix for should not appeared directory hard link liu.song11
2014-11-05 11:45 ` Brian Norris
2014-11-11 7:12 ` liu.song11
2014-11-12 6:45 ` Liu Song
2014-12-17 1:53 ` Brian Norris
2014-12-17 2:02 ` nick [this message]
2015-02-12 13:43 ` David Woodhouse
2015-02-13 4:09 ` liu.song11
2015-02-13 10:13 ` David Woodhouse
2015-02-13 11:28 ` David Woodhouse
2015-03-12 3:05 ` liu.song11
[not found] <OF2CCB8417.29770A56-ON48257EE5.0004DBEE-48257EE5.0004E5CC@LocalDomain>
2015-10-26 3:19 ` deng.chao1
2016-02-01 14:21 ` David Woodhouse
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=5490E436.7020200@gmail.com \
--to=xerofoify@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=cui.yunfeng@zte.com.cn \
--cc=dedekind1@gmail.com \
--cc=deng.chao1@zte.com.cn \
--cc=dwmw2@infradead.org \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-mtd@lists.infradead.org \
--cc=liu.song11@zte.com.cn \
--cc=wang.bo116@zte.com.cn \
/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