qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Kerr <jeremy.kerr@canonical.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss@lists.ozlabs.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC PATCH] devicetree: Fix buffer overflow on setting device node name
Date: Thu, 8 Apr 2010 11:48:01 +0800	[thread overview]
Message-ID: <201004081148.02064.jeremy.kerr@canonical.com> (raw)
In-Reply-To: <20100408015013.18100.89239.stgit@angua>

Hi Grant,

Thanks, this fixes the overflow for me too. Have applied to my tree and pushed 
out.

If anyone else would like to check out out the patches, my tree is at:

  http://kernel.ubuntu.com/git?p=jk/dt/qemu.git;a=summary
  git://kernel.ubuntu.com/jk/dt/qemu.git

Cheers,


Jeremy

      reply	other threads:[~2010-04-08  3:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  1:51 [Qemu-devel] [RFC PATCH] devicetree: Fix buffer overflow on setting device node name Grant Likely
2010-04-08  3:48 ` Jeremy Kerr [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=201004081148.02064.jeremy.kerr@canonical.com \
    --to=jeremy.kerr@canonical.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --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).