From: Michael Tokarev <mjt@tls.msk.ru>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] bt: check struct sizes
Date: Sun, 29 Nov 2015 13:40:25 +0300 [thread overview]
Message-ID: <565AD619.70103@msgid.tls.msk.ru> (raw)
In-Reply-To: <5659C4B5.8030108@redhat.com>
28.11.2015 18:13, Paolo Bonzini wrote:
> On 27/11/2015 18:57, Paolo Bonzini wrote:
>> See http://permalink.gmane.org/gmane.linux.bluez.kernel/36505. For historical
>> reasons these do not use sizeof, and Coverity caught a mistake in
>> EVT_ENCRYPT_CHANGE_SIZE.
>>
>> Note other sizes that seem wrong or inconsistent with the kernel header.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Hmm, can do better...
Can do, or will do, or?
Note we've lost last S-o-b (by Markus) as well ;)
/mjt
prev parent reply other threads:[~2015-11-29 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 17:57 [Qemu-devel] [PATCH v2] bt: check struct sizes Paolo Bonzini
2015-11-28 15:13 ` Paolo Bonzini
2015-11-29 10:40 ` Michael Tokarev [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=565AD619.70103@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).