From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-1.2] msix: make [un]use vectors on reset/load optional
Date: Thu, 30 Aug 2012 17:39:27 +0300 [thread overview]
Message-ID: <20120830143927.GC21646@redhat.com> (raw)
In-Reply-To: <503F6BF2.7050704@suse.de>
On Thu, Aug 30, 2012 at 03:34:42PM +0200, Andreas Färber wrote:
> Am 29.08.2012 20:13, schrieb Michael S. Tsirkin:
> > On Wed, Aug 29, 2012 at 06:54:35PM +0200, Andreas Färber wrote:
> >> $subject: "[un]used vectors"? -- could be fixed by committer.
> >
> > Sorry I don't unedrstand. it's not 'unused': it's use and unuse.
> > What is wrong with the subject?
>
> The grammar with two verbs "make [un]use" sounded wrong to my ears.
> Given your explanation of [un]use above, did you mean "make clearing
> [un]use vectors optional on reset/load" or something like that?
>
> /-F
No, sorry. What is meant is simply functions
msix_vector_use/msix_vector_unuse:
calling these on reset/load was required but
is now optional.
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-08-30 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 16:40 [Qemu-devel] [PATCH for-1.2] msix: make [un]use vectors on reset/load optional Michael S. Tsirkin
2012-08-29 16:44 ` Jan Kiszka
2012-08-29 16:47 ` Michael S. Tsirkin
2012-08-29 16:59 ` Cam Macdonell
2012-08-29 16:54 ` Andreas Färber
2012-08-29 18:13 ` Michael S. Tsirkin
2012-08-30 13:34 ` Andreas Färber
2012-08-30 14:39 ` Michael S. Tsirkin [this message]
2012-08-29 17:17 ` Cam Macdonell
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=20120830143927.GC21646@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=alex.williamson@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.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).