qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: P J P <ppandit@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Ling Liu <liuling-it@360.cn>
Subject: Re: [Qemu-devel] [PATCH] i386: avoid null pointer dereference
Date: Thu, 7 Jan 2016 19:00:12 +0530 (IST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1601071859100.14967@wniryva> (raw)
In-Reply-To: <568E5C57.7090309@redhat.com>

+-- On Thu, 7 Jan 2016, Paolo Bonzini wrote --+
| On 04/01/2016 16:49, P J P wrote:
| > Ping..! -> https://patchwork.ozlabs.org/patch/558748/
| 
| I was on vacation until today.  I'll send a pull request some time next
| week.

Sure okay, thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F

      reply	other threads:[~2016-01-07 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18  6:05 [Qemu-devel] [PATCH] i386: avoid null pointer dereference P J P
2016-01-04 15:49 ` P J P
2016-01-07 12:38   ` Paolo Bonzini
2016-01-07 13:30     ` P J P [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=alpine.LFD.2.20.1601071859100.14967@wniryva \
    --to=ppandit@redhat.com \
    --cc=liuling-it@360.cn \
    --cc=pbonzini@redhat.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).