All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Richard Henderson <rth@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [for-1.7] hw/i386/acpi-build.c vs glib-2.12
Date: Thu, 21 Nov 2013 13:25:26 +0200	[thread overview]
Message-ID: <20131121112526.GA31128@redhat.com> (raw)
In-Reply-To: <CAFEAcA9wLt6pWgFaMdfLkR3=QA6_ifrL4_4MJG0qvDtuV8-Hiw@mail.gmail.com>

On Thu, Nov 21, 2013 at 10:09:58AM +0000, Peter Maydell wrote:
> On 21 November 2013 09:15, Michael S. Tsirkin <mst@redhat.com> wrote:
> > diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> > index 486e705..97e0fba 100644
> > --- a/hw/i386/acpi-build.c
> > +++ b/hw/i386/acpi-build.c
> > @@ -287,14 +287,17 @@ static inline void build_append_array(GArray *array, GArray *val)
> >
> >  static void build_append_nameseg(GArray *array, const char *format, ...)
> >  {
> > -    GString *s = g_string_new("");
> > +    /* It would be nicer to use g_string_vprintf but it's only there in 2.22 */
> > +    char s[] = "XXXX";
> > +    int len;
> >      va_list args;
> >
> >      va_start(args, format);
> >      g_string_vprintf(s, format, args);
> > +    len = vsnprintf(s, sizeof s, format, args);
> >      va_end(args);
> 
> ...this patch doesn't seem to have removed the g_string_vprintf
> call?
> 
> thanks
> -- PMM

yes and I found more issues.
Pls don't test yet I'll post v2.

      reply	other threads:[~2013-11-21 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 20:49 [Qemu-devel] [for-1.7] hw/i386/acpi-build.c vs glib-2.12 Richard Henderson
2013-11-18 22:57 ` Michael S. Tsirkin
2013-11-21  9:15 ` Michael S. Tsirkin
2013-11-21 10:09   ` Peter Maydell
2013-11-21 11:25     ` Michael S. Tsirkin [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=20131121112526.GA31128@redhat.com \
    --to=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@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.