From: Mike Christie <michael.christie@oracle.com>
To: target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
stefanha@redhat.com, pbonzini@redhat.com, jasowang@redhat.com,
mst@redhat.com, sgarzare@redhat.com,
virtualization@lists.linux-foundation.org
Subject: vhost: coding style and flush cleanups
Date: Tue, 25 May 2021 12:47:28 -0500 [thread overview]
Message-ID: <20210525174733.6212-1-michael.christie@oracle.com> (raw)
The following patches apply over linus's tree and mst's vhost branch.
The patches are just some flush cleanups and a patch to reduce flush
calls and some coding style fixups.
My worker threading patches are built over these patches, but they seem
like patches that would be ok even if the threading patches never get
merged, so I've broken them out to make the threading patchset easier to
review.
V2:
- Added vhost_work coding style cleanup patch. The worker threading
patchset modifies that code. I thought I would clean it up since my
patch that added a new field looked weird using different styles.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next reply other threads:[~2021-05-25 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 17:47 Mike Christie [this message]
2021-05-25 17:47 ` [PATCH 1/5] vhost: remove work arg from vhost_work_flush Mike Christie
2021-05-27 13:22 ` Stefano Garzarella
2021-05-25 17:47 ` [PATCH 2/5] vhost-scsi: remove extra flushes Mike Christie
2021-05-25 17:47 ` [PATCH 3/5] vhost-scsi: reduce flushes during endpoint clearing Mike Christie
2021-05-25 17:47 ` [PATCH 4/5] vhost: fix poll coding style Mike Christie
2021-05-25 17:47 ` [PATCH 5/5] vhost: fix up vhost_work " Mike Christie
2021-05-27 13:23 ` Stefano Garzarella
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=20210525174733.6212-1-michael.christie@oracle.com \
--to=michael.christie@oracle.com \
--cc=jasowang@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=target-devel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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 NNTP newsgroup(s).