From: Bart Van Assche <bvanassche@acm.org>
To: Yang Xiuwei <yangxiuwei@kylinos.cn>
Cc: axboe@kernel.dk, fujita.tomonori@lab.ntt.co.jp,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v7 3/3] scsi: bsg: add io_uring passthrough handler
Date: Fri, 13 Mar 2026 08:37:13 -0700 [thread overview]
Message-ID: <aa1e0517-3b90-4c14-aaac-d0f9526e088d@acm.org> (raw)
In-Reply-To: <20260313073415.102437-3-yangxiuwei@kylinos.cn>
On 3/13/26 12:34 AM, Yang Xiuwei wrote:
> In particular, when there is a
> tension between keeping the reverse Christmas tree order and making
> data/control dependencies explicit in the declaration order, I would
> very much appreciate your advice on how to handle such cases, so that I
> can do better here and in future patches.
I think that combining declarations and initializations is considered
more important than strictly ordering declarations from longest to
shortest.
Thanks,
Bart.
prev parent reply other threads:[~2026-03-13 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 9:22 [PATCH v7 0/3] bsg: add io_uring command support for SCSI passthrough Yang Xiuwei
2026-03-12 9:22 ` [PATCH v7 1/3] bsg: add bsg_uring_cmd uapi structure Yang Xiuwei
2026-03-12 19:29 ` Bart Van Assche
2026-03-13 7:34 ` Yang Xiuwei
2026-03-13 15:34 ` Bart Van Assche
2026-03-12 9:22 ` [PATCH v7 2/3] bsg: add io_uring command support to generic layer Yang Xiuwei
2026-03-12 19:33 ` Bart Van Assche
2026-03-13 7:34 ` Yang Xiuwei
2026-03-13 15:35 ` Bart Van Assche
2026-03-12 9:22 ` [PATCH v7 3/3] scsi: bsg: add io_uring passthrough handler Yang Xiuwei
2026-03-12 19:41 ` Bart Van Assche
2026-03-13 7:34 ` Yang Xiuwei
2026-03-13 15:37 ` Bart Van Assche [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=aa1e0517-3b90-4c14-aaac-d0f9526e088d@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yangxiuwei@kylinos.cn \
/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