From: patchwork-bot+f2fs@kernel.org
To: Sheng Yong <shengyong@oppo.com>
Cc: ebiggers@kernel.org, jaegeuk@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v4 0/6] f2fs: add f2fs_ioc_[get|set]_extra_attr
Date: Thu, 15 Jun 2023 18:00:22 +0000 [thread overview]
Message-ID: <168685202293.7502.5200872561131261330.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230612030121.2393541-1-shengyong@oppo.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 12 Jun 2023 11:01:15 +0800 you wrote:
> This patchset introduces two ioctls to get or modify values in
> f2fs_inode's extra attribute area:
> * f2fs_ioc_get_extra_attr
> * f2fs_ioc_set_extra_attr
>
> The argument of these two ioctls is `struct f2fs_extra_attr', which has
> three members:
> * field: indicates which field in extra attribute area is handled
> * attr: value or userspace pointer
> * attr_size: size of `attr'
>
> [...]
Here is the summary with links:
- [f2fs-dev,v4,1/6] f2fs: add helper to check compression level
(no matching commit)
- [f2fs-dev,v4,2/6] f2fs: cleanup MIN_INLINE_XATTR_SIZE
https://git.kernel.org/jaegeuk/f2fs/c/4acc6b9d6104
- [f2fs-dev,v4,3/6] f2fs: add helper to get inode chksum from inode page
(no matching commit)
- [f2fs-dev,v4,4/6] f2fs: add f2fs_ioc_get_compress_blocks
https://git.kernel.org/jaegeuk/f2fs/c/1c5c646596c6
- [f2fs-dev,v4,5/6] f2fs: add f2fs_ioc_[get|set]_extra_attr
(no matching commit)
- [f2fs-dev,v4,6/6] f2fs: access compression level and flags by extra attr ioctls
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-06-15 18:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 3:01 [f2fs-dev] [PATCH v4 0/6] f2fs: add f2fs_ioc_[get|set]_extra_attr Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 1/6] f2fs: add helper to check compression level Sheng Yong via Linux-f2fs-devel
2023-06-12 22:14 ` Jaegeuk Kim
2023-06-13 1:48 ` Chao Yu
2023-06-13 2:28 ` Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 2/6] f2fs: cleanup MIN_INLINE_XATTR_SIZE Sheng Yong via Linux-f2fs-devel
2023-06-13 1:48 ` Chao Yu
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 3/6] f2fs: add helper to get inode chksum from inode page Sheng Yong via Linux-f2fs-devel
2023-06-13 1:52 ` Chao Yu
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 4/6] f2fs: add f2fs_ioc_get_compress_blocks Sheng Yong via Linux-f2fs-devel
2023-06-13 1:53 ` Chao Yu
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 5/6] f2fs: add f2fs_ioc_[get|set]_extra_attr Sheng Yong via Linux-f2fs-devel
2023-06-12 15:47 ` Jaegeuk Kim
2023-06-13 1:53 ` Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 6/6] f2fs: access compression level and flags by extra attr ioctls Sheng Yong via Linux-f2fs-devel
2023-06-15 18:00 ` patchwork-bot+f2fs [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=168685202293.7502.5200872561131261330.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shengyong@oppo.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).