From: "Juan José Arboleda" <soyjuanarbol@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux.dev
Subject: Re: [PATCH] virtio: Fix various coding style issues
Date: Wed, 24 Jul 2024 12:22:07 -0500 [thread overview]
Message-ID: <ZqE4P1EjiLI9iQj-@fedora> (raw)
In-Reply-To: <20240724100022-mutt-send-email-mst@kernel.org>
> Makes backports harder for little gain.
> Code gets tweaked naturally as someone works on it.
I understand your concern about backports. However, this patch only updates
the coding style to match kernel-wide standards without altering behavior.
Consistent style improves readability and maintainability without impacting
functionality, thus not complicating backports.
Thank you for considering this.
Best,
- Juan José
next prev parent reply other threads:[~2024-07-24 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 5:46 [PATCH] virtio: Fix various coding style issues Juan José Arboleda
2024-07-19 17:48 ` Eugenio Perez Martin
2024-07-19 18:11 ` Michael S. Tsirkin
2024-07-19 22:28 ` Juan José Arboleda
2024-07-24 14:01 ` Michael S. Tsirkin
2024-07-24 17:22 ` Juan José Arboleda [this message]
2024-07-25 6:02 ` Michael S. Tsirkin
2024-07-19 22:17 ` Juan José Arboleda
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=ZqE4P1EjiLI9iQj-@fedora \
--to=soyjuanarbol@gmail.com \
--cc=mst@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;
as well as URLs for NNTP newsgroup(s).