IO-Uring Archive mirror
 help / color / mirror / Atom feed
From: Xin Wang <yw987194828@gmail.com>
To: axboe@kernel.dk
Cc: asml.silence@gmail.com, io-uring@vger.kernel.org,
	linux-kernel@vger.kernel.org, Xin Wang <yw987194828@163.com>
Subject: [PATCH v2 0/1] io_uring: extract the function that checks the legitimacy of sq/cq entries
Date: Fri, 15 Mar 2024 05:21:16 +0800	[thread overview]
Message-ID: <20240314212117.108464-1-yw987194828@163.com> (raw)


Xin Wang (1):
  It was really careless of me, earlier I wanted to keep the coding style
  as close as possible to the rest of the code, so I looked for similar
  code, e.g., line 4713 of kernel/trace/ring_buffer.c: if (ts && ! (*ts))
  and line 1178 of ipc/shm.c: audit_ipc_obj(&(shp->shm_perm)). Now I removed
  the brackets and it passes the checkpatch.pl script, thanks!

--
2.25.1

             reply	other threads:[~2024-03-14 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 21:21 Xin Wang [this message]
2024-03-14 21:21 ` [PATCH v2 1/1] io_uring: extract the function that checks the legitimacy of sq/cq entries Xin Wang

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=20240314212117.108464-1-yw987194828@163.com \
    --to=yw987194828@gmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yw987194828@163.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 read-only IMAP folder(s) and NNTP newsgroup(s).