All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs_io: add ioprio command to give a io priority hint
Date: Mon, 3 Mar 2025 11:18:20 +0800	[thread overview]
Message-ID: <c0f962c9-4946-4347-b26f-5bd4863aad47@kernel.org> (raw)
In-Reply-To: <20250228190854.422890-2-jaegeuk@kernel.org>

On 3/1/25 03:08, Jaegeuk Kim via Linux-f2fs-devel wrote:
> This adds a command to call ioctl(F2FS_IOC_IO_PRIO).
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2025-03-03  3:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 19:08 [f2fs-dev] [PATCH 1/2] f2fs_io: support fadvise dontneed, random, and noreuse Jaegeuk Kim via Linux-f2fs-devel
2025-02-28 19:08 ` [f2fs-dev] [PATCH 2/2] f2fs_io: add ioprio command to give a io priority hint Jaegeuk Kim via Linux-f2fs-devel
2025-03-03  3:18   ` Chao Yu via Linux-f2fs-devel [this message]
2025-03-03  3:17 ` [f2fs-dev] [PATCH 1/2] f2fs_io: support fadvise dontneed, random, and noreuse Chao Yu via Linux-f2fs-devel
  -- strict thread matches above, loose matches on Subject: below --
2025-02-13 18:01 Jaegeuk Kim via Linux-f2fs-devel
2025-02-13 18:01 ` [f2fs-dev] [PATCH 2/2] f2fs_io: add ioprio command to give a io priority hint Jaegeuk Kim via Linux-f2fs-devel

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=c0f962c9-4946-4347-b26f-5bd4863aad47@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.