From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <chao@kernel.org>
Subject: Re: [PATCH v3 RESEND] f2fs: support F2FS_IOC_PRECACHE_EXTENTS
Date: Wed, 17 Jan 2018 09:28:56 +0800 [thread overview]
Message-ID: <5c9dfe2c-9507-dfe4-72ec-5518f7cf866d@huawei.com> (raw)
In-Reply-To: <20180116235908.GA22625@jaegeuk-macbookpro.roam.corp.google.com>
Hi Jaegeuk,
On 2018/1/17 7:59, Jaegeuk Kim wrote:
> Since I needed to add F2FS_IOC_GET_PIN_FILE, let me modify the ioctl number to:
>
> #define F2FS_IOC_PRECACHE_EXTENTS _IO(F2FS_IOCTL_MAGIC, 15)
No problem. :)
Thanks,
prev parent reply other threads:[~2018-01-17 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 6:42 Chao Yu
2018-01-16 23:59 ` Jaegeuk Kim
2018-01-17 1:28 ` 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=5c9dfe2c-9507-dfe4-72ec-5518f7cf866d@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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®