From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org, Eugenio Perez Martin <eperezma@redhat.com>,
German Maglione <gmaglione@redhat.com>,
Liu Jiang <gerry@linux.alibaba.com>,
Sergio Lopez Pascual <slp@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH v3 1/7] vhost-user: strip superfluous whitespace
Date: Wed, 4 Oct 2023 08:54:45 -0400 [thread overview]
Message-ID: <20231004085350-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <5f265558-71ae-7371-9fbb-dd0cfe1c69fd@redhat.com>
On Wed, Oct 04, 2023 at 12:08:52PM +0200, Laszlo Ersek wrote:
> On 10/4/23 11:06, Michael S. Tsirkin wrote:
> > On Mon, Oct 02, 2023 at 10:32:15PM +0200, Laszlo Ersek wrote:
> >> Cc: "Michael S. Tsirkin" <mst@redhat.com> (supporter:vhost)
> >
> > why the (supporter:vhost) part? not all scripts will cope
> > well with text after the mail. If you really want to keep
> > it around, I think you should add a hash tag # before that -
> > more tools know to ignore that.
>
> It looked too tiresome to strip all these comments, plus I expected
> that, if the get_maintainer.pl script output these lines, they were fit
> for inclusion in "Cc:" tags in the commit message.
>
> If they're not, then the tool should indeed insert a # in-between, or
> else provide the explanation for each name+email printed on separate
> (preceding) lines, potentially prefixed with "#". That makes for easy
> human reading and also for easy machine reading (filtering them out).
>
> Laszlo
/me shrugs
get_maintainer.pl doesn't output Cc tags either. Just pipe to
sed 's/(.*//' ?
> >
> >
> >> Cc: Eugenio Perez Martin <eperezma@redhat.com>
> >> Cc: German Maglione <gmaglione@redhat.com>
> >> Cc: Liu Jiang <gerry@linux.alibaba.com>
> >> Cc: Sergio Lopez Pascual <slp@redhat.com>
> >> Cc: Stefano Garzarella <sgarzare@redhat.com>
> >> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> >> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> >> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> >> Tested-by: Albert Esteve <aesteve@redhat.com>
> >> Reviewed-by: Eugenio Pérez <eperezma@redhat.com>
> >> ---
> >>
> >> Notes:
> >> v3:
> >>
> >> - pick up R-b from Phil and Eugenio, T-b from Albert
> >>
> >> v2:
> >>
> >> - pick up Stefano's R-b
> >>
> >> hw/virtio/vhost-user.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
> >> index 8dcf049d422b..b4b677c1ce66 100644
> >> --- a/hw/virtio/vhost-user.c
> >> +++ b/hw/virtio/vhost-user.c
> >> @@ -398,7 +398,7 @@ static int vhost_user_write(struct vhost_dev *dev, VhostUserMsg *msg,
> >> * operations such as configuring device memory mappings or issuing device
> >> * resets, which affect the whole device instead of individual VQs,
> >> * vhost-user messages should only be sent once.
> >> - *
> >> + *
> >> * Devices with multiple vhost_devs are given an associated dev->vq_index
> >> * so per_device requests are only sent if vq_index is 0.
> >> */
> >>
> >
next prev parent reply other threads:[~2023-10-04 12:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 20:32 [PATCH v3 0/7] vhost-user: call VHOST_USER_SET_VRING_ENABLE synchronously Laszlo Ersek
2023-10-02 20:32 ` [PATCH v3 1/7] vhost-user: strip superfluous whitespace Laszlo Ersek
2023-10-04 9:06 ` Michael S. Tsirkin
2023-10-04 10:08 ` Laszlo Ersek
2023-10-04 12:54 ` Michael S. Tsirkin [this message]
2023-10-04 13:28 ` Laszlo Ersek
2023-10-02 20:32 ` [PATCH v3 2/7] vhost-user: tighten "reply_supported" scope in "set_vring_addr" Laszlo Ersek
2023-10-02 20:32 ` [PATCH v3 3/7] vhost-user: factor out "vhost_user_write_sync" Laszlo Ersek
2023-10-02 20:32 ` [PATCH v3 4/7] vhost-user: flatten "enforce_reply" into "vhost_user_write_sync" Laszlo Ersek
2023-10-02 20:32 ` [PATCH v3 5/7] vhost-user: hoist "write_sync", "get_features", "get_u64" Laszlo Ersek
2023-10-02 20:32 ` [PATCH v3 6/7] vhost-user: allow "vhost_set_vring" to wait for a reply Laszlo Ersek
2023-10-02 20:32 ` [PATCH v3 7/7] vhost-user: call VHOST_USER_SET_VRING_ENABLE synchronously Laszlo Ersek
2023-10-18 11:26 ` [PATCH v3 0/7] " Laszlo Ersek
2023-10-18 11:41 ` Stefan Hajnoczi
2023-10-18 11:59 ` Michael S. Tsirkin
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=20231004085350-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=gerry@linux.alibaba.com \
--cc=gmaglione@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.