mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 1/2 v3] f2fs: expose /sys/fs/f2fs/features
Date: Sat, 29 Jul 2017 08:23:14 +0800	[thread overview]
Message-ID: <8d080265-4ec5-3a4e-408d-9dae57984d62@huawei.com> (raw)
In-Reply-To: <20170728194134.GC27548@jaegeuk-macbookpro.roam.corp.google.com>

On 2017/7/29 3:41, Jaegeuk Kim wrote:
>  Change log from v2:
>   - add missing new features
>   - fix print out features
> 
>  Change log from v1:
>   - add /sys/fs/f2fs/dev/features
> 
>>From cf512bfeed89d760138ade12014f17fc5779ca04 Mon Sep 17 00:00:00 2001
> From: Jaegeuk Kim <jaegeuk@kernel.org>
> Date: Fri, 21 Jul 2017 17:14:09 -0700
> Subject: [PATCH] f2fs: expose features to sysfs entry
> 
> This patch exposes what features are supported by current f2fs build to sysfs
> entry via:
> 
> /sys/fs/f2fs/features/
> /sys/fs/f2fs/dev/features
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

      reply	other threads:[~2017-07-29  0:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26  1:29 [PATCH 1/2] " Jaegeuk Kim
2017-07-26  1:29 ` [PATCH 2/2] f2fs: don't give partially written atomic data from process crash Jaegeuk Kim
2017-07-26 14:07   ` [f2fs-dev] " Chao Yu
2017-07-26 14:31 ` [f2fs-dev] [PATCH 1/2] f2fs: expose /sys/fs/f2fs/features Chao Yu
2017-07-26 21:43   ` Jaegeuk Kim
2017-07-27  5:36     ` Chao Yu
2017-07-26 21:44 ` [PATCH 1/2 v2] " Jaegeuk Kim
2017-07-28 12:40   ` [f2fs-dev] " Chao Yu
2017-07-28 19:41   ` [f2fs-dev] [PATCH 1/2 v3] " Jaegeuk Kim
2017-07-29  0:23     ` 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=8d080265-4ec5-3a4e-408d-9dae57984d62@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --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
all inboxes | Powered by JetHome®