From: Jens Axboe <axboe@kernel.dk>
To: yunlong xing <yunlongxing23@gmail.com>,
Yunlong Xing <yunlong.xing@unisoc.com>
Cc: linux-block@vger.kernel.org, bvanassche@acm.org, hch@lst.de,
niuzhiguo84@gmail.com, linux-kernel@vger.kernel.org,
hao_hao.wang@unisoc.com
Subject: Re: [PATCH V3] loop: aio inherit the ioprio of original request
Date: Tue, 15 Apr 2025 07:45:48 -0600 [thread overview]
Message-ID: <9db33edf-8cdf-42e1-bf82-da9362100d83@kernel.dk> (raw)
In-Reply-To: <CA+3AYtRRgL2-vPNm=1XBKd_PFuRcB5fZh96VGsfTO2VaAvqv9w@mail.gmail.com>
On 4/14/25 11:56 PM, yunlong xing wrote:
> There is a mistake of Signed-off-by in commit message on previous
> version. I noticed that you had commited it in block-6.15. Could you
> please help fix it.
I fixed it up.
--
Jens Axboe
next prev parent reply other threads:[~2025-04-15 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 5:44 [PATCH V3] loop: aio inherit the ioprio of original request Yunlong Xing
2025-04-15 5:56 ` yunlong xing
2025-04-15 13:45 ` Jens Axboe [this message]
2025-04-15 15:38 ` Chaitanya Kulkarni
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=9db33edf-8cdf-42e1-bf82-da9362100d83@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hao_hao.wang@unisoc.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=yunlong.xing@unisoc.com \
--cc=yunlongxing23@gmail.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