From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Joseph Trebbien <jtrebbien@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Outdated comment in HACKING
Date: Fri, 25 Feb 2011 23:21:18 +0100 [thread overview]
Message-ID: <4D682B5E.3080201@mail.berlios.de> (raw)
In-Reply-To: <4D682866.9070005@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
Am 25.02.2011 23:08, schrieb Anthony Liguori:
> This patch won't apply with git-am because your mailer is doing weird
> things. Please use git-send-email to send the patch.
>
> Regards,
>
> Anthony Liguori
>
> On 02/24/2011 06:27 PM, Joey Trebbien wrote:
>> All printf-style functions in the source (except for a few in tests/)
>> already have a format __attribute__ (via the GCC_ATTR or GCC_FMT_ATTR
>> macros).
>>
>> Signed-off-by: Joseph Trebbien <jtrebbien@gmail.com
>> <mailto:jtrebbien@gmail.com>>
>> ---
>> HACKING | 3 ---
>> 1 files changed, 0 insertions(+), 3 deletions(-)
>>
>>
>> diff --git a/HACKING b/HACKING
>> index 6ba9d7e..3af53fd 100644
>> --- a/HACKING
>> +++ b/HACKING
>> @@ -120,6 +120,3 @@ gcc's printf attribute directive in the prototype.
>> This makes it so gcc's -Wformat and -Wformat-security options can do
>> their jobs and cross-check format strings with the number and types
>> of arguments.
>> -
>> -Currently many functions in QEMU are not following this rule but
>> -patches to add the attribute would be very much appreciated.
>
Hi Anthony,
the same patch is on my list of missing patches which I had sent
weeks ago, so no need for Joey to resent his patch.
I'll resend my version.
Regards,
Stefan W.
[-- Attachment #2: Type: text/html, Size: 2012 bytes --]
prev parent reply other threads:[~2011-02-25 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 0:27 [Qemu-devel] [PATCH] Outdated comment in HACKING Joey Trebbien
2011-02-25 22:08 ` Anthony Liguori
2011-02-25 22:21 ` Stefan Weil [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=4D682B5E.3080201@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=anthony@codemonkey.ws \
--cc=jtrebbien@gmail.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 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.