From: michael.christie@oracle.com
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
mst@redhat.com, jasowang@redhat.com, pbonzini@redhat.com,
stefanha@redhat.com, eperezma@redhat.com,
virtualization@lists.linux.dev, kvm@vger.kernel.org
Cc: darren.kenny@oracle.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] vhost-scsi: Fix typos and formatting in comments and logs
Date: Wed, 11 Jun 2025 21:30:01 -0500 [thread overview]
Message-ID: <9273cb5b-08d1-44b0-8365-b624ded633c4@oracle.com> (raw)
In-Reply-To: <20250611143932.2443796-1-alok.a.tiwari@oracle.com>
On 6/11/25 9:39 AM, Alok Tiwari wrote:
> This patch corrects several minor typos and formatting issues.
> Changes include:
>
> Fixing misspellings like in comments
> - "explict" -> "explicit"
> - "infight" -> "inflight",
> - "with generate" -> "will generate"
>
> formatting in logs
> - Correcting log formatting specifier from "%dd" to "%d"
> - Adding a missing space in the sysfs emit string to prevent
> misinterpreted output like "X86_64on ". changing to "X86_64 on "
> - Cleaning up stray semicolons in struct definition endings
>
> These changes improve code readability and consistency.
> no functionality changes.
>
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
Reviewed-by: Mike Christie <michael.christie@oracle.com>
prev parent reply other threads:[~2025-06-12 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 14:39 [PATCH 1/2] vhost-scsi: Fix typos and formatting in comments and logs Alok Tiwari
2025-06-11 14:39 ` [PATCH 2/2] vhost-scsi: Improve error handling in vhost_scsi_make_nexus and tpg Alok Tiwari
2025-06-11 18:17 ` Stefan Hajnoczi
2025-06-12 2:29 ` michael.christie
2025-06-11 18:09 ` [PATCH 1/2] vhost-scsi: Fix typos and formatting in comments and logs Stefan Hajnoczi
2025-06-12 2:30 ` michael.christie [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=9273cb5b-08d1-44b0-8365-b624ded633c4@oracle.com \
--to=michael.christie@oracle.com \
--cc=alok.a.tiwari@oracle.com \
--cc=darren.kenny@oracle.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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