From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Haiyue Wang <haiyuewa@163.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] io_uring: use tab indentation for IORING_SEND_VECTORIZED comment
Date: Tue, 07 Oct 2025 08:04:45 -0600 [thread overview]
Message-ID: <175984588596.1934259.1809567091954753640.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251007061822.21220-1-haiyuewa@163.com>
On Tue, 07 Oct 2025 14:18:18 +0800, Haiyue Wang wrote:
> Be consistent with tab style of "liburing/src/include/liburing/io_uring.h".
>
>
Applied, thanks!
[1/1] io_uring: use tab indentation for IORING_SEND_VECTORIZED comment
commit: beb97995b97532e1f215e3295e6843e59862f94b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-10-07 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 6:18 [PATCH v1] io_uring: use tab indentation for IORING_SEND_VECTORIZED comment Haiyue Wang
2025-10-07 14:04 ` Jens Axboe [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=175984588596.1934259.1809567091954753640.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=haiyuewa@163.com \
--cc=io-uring@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).