From: Jens Axboe <axboe@kernel.dk>
To: Damien Le Moal <damien.lemoal@wdc.com>,
linux-block@vger.kernel.org,
Paolo Valente <paolo.valente@linaro.org>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Subject: Re: [f2fs-dev] [PATCH v4 0/6] IO priority fixes and improvements
Date: Wed, 18 Aug 2021 07:24:10 -0600 [thread overview]
Message-ID: <e998936b-5452-1048-80f2-4161bb77b3de@kernel.dk> (raw)
In-Reply-To: <20210811033702.368488-1-damien.lemoal@wdc.com>
On 8/10/21 9:36 PM, Damien Le Moal wrote:
> This series fixes problems with IO priority values handling and cleans
> up several macro names and code for clarity.
Applied for 5.15 - note that I dropped the lightnvm change from 6/6,
as it isn't strictly needed and lightnvm is deleted from the 5.15
drivers branch anyway.
--
Jens Axboe
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-08-18 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 3:36 [f2fs-dev] [PATCH v4 0/6] IO priority fixes and improvements Damien Le Moal
2021-08-11 3:36 ` [f2fs-dev] [PATCH v4 1/6] block: bfq: fix bfq_set_next_ioprio_data() Damien Le Moal
2021-08-11 3:36 ` [f2fs-dev] [PATCH v4 2/6] block: improve ioprio class description comment Damien Le Moal
2021-08-11 3:36 ` [f2fs-dev] [PATCH v4 3/6] block: change ioprio_valid() to an inline function Damien Le Moal
2021-08-11 7:56 ` Johannes Thumshirn
2021-08-11 8:51 ` Damien Le Moal
2021-08-11 9:14 ` Johannes Thumshirn
2021-08-11 3:37 ` [f2fs-dev] [PATCH v4 4/6] block: fix IOPRIO_PRIO_CLASS() and IOPRIO_PRIO_VALUE() macros Damien Le Moal
2021-08-11 3:37 ` [f2fs-dev] [PATCH v4 5/6] block: Introduce IOPRIO_NR_LEVELS Damien Le Moal
2021-08-11 3:37 ` [f2fs-dev] [PATCH v4 6/6] block: fix default IO priority handling Damien Le Moal
2021-08-18 9:53 ` [f2fs-dev] [PATCH v4 0/6] IO priority fixes and improvements Damien Le Moal
2021-08-18 13:24 ` Jens Axboe [this message]
2021-08-18 21:52 ` Damien Le Moal
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=e998936b-5452-1048-80f2-4161bb77b3de@kernel.dk \
--to=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=paolo.valente@linaro.org \
--cc=yuchao0@huawei.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).