From: Stefan Hajnoczi <stefanha@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Manuel Egele <megele@bu.edu>, qemu-devel <qemu-devel@nongnu.org>,
Alexander Oleinik <alxndr@bu.edu>, Bandan Das <bsd@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [qemu-web PATCH] Add device fuzzing blog post
Date: Thu, 21 Nov 2019 12:51:28 +0000 [thread overview]
Message-ID: <20191121125128.GT439743@stefanha-x1.localdomain> (raw)
In-Reply-To: <9313c9d8-440c-03d9-4050-064c0a2b7ced@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Tue, Nov 12, 2019 at 12:39:49PM +0100, Thomas Huth wrote:
> On 07/11/2019 16.48, Stefan Hajnoczi wrote:
> > On Thu, Nov 7, 2019 at 10:43 AM Thomas Huth <thuth@redhat.com> wrote:
> >>
> >> ----- Original Message -----
> >>> From: "Stefan Hajnoczi" <stefanha@redhat.com>
> >>> Sent: Thursday, November 7, 2019 10:11:36 AM
> >>>
> >>> This blog post covers the device fuzzing GSoC project that Alexander
> >>> Olenik did in 2019.
> [...]
> >> Seems like the images are missing ... can you please attach them?
> >
> > The commit is available with .png files here:
> > https://github.com/stefanha/qemu-web/commit/49efe1b254460a92c6348e1981caf3e1320782f8
> >
> > I moved the authorship information into the author: field.
>
> The article is online now:
>
> https://www.qemu.org/2019/11/07/device-fuzzing/
Thank you!
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-11-21 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 9:11 [qemu-web PATCH] Add device fuzzing blog post Stefan Hajnoczi
2019-11-07 9:41 ` Thomas Huth
2019-11-07 15:48 ` Stefan Hajnoczi
2019-11-12 11:39 ` Thomas Huth
2019-11-21 12:51 ` Stefan Hajnoczi [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=20191121125128.GT439743@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=megele@bu.edu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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 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).