qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Alexander Bulekov <alxndr@bu.edu>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/7] 2021-01-20 fuzzing patches
Date: Fri, 22 Jan 2021 15:06:28 +0000	[thread overview]
Message-ID: <CAFEAcA8QNMiFe5p=-agvvnfFY_teMR3s-8AfT3OEa6GCK-Y=kg@mail.gmail.com> (raw)
In-Reply-To: <20210120174456.275312-1-alxndr@bu.edu>

On Wed, 20 Jan 2021 at 17:45, Alexander Bulekov <alxndr@bu.edu> wrote:
>
> Hi Peter,
>
> The following changes since commit 48202c712412c803ddb56365c7bca322aa4e7506:
>
>   Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20210119-1' into staging (2021-01-19 15:47:23 +0000)
>
> are available in the Git repository at:
>
>   https://gitlab.com/a1xndr/qemu.git tags/pull-request-2021-01-20
>
> for you to fetch changes up to fae446ae7b6f746377186b3e19fd3f732a8b4325:
>
>   fuzz: add virtio-9p configurations for fuzzing (2021-01-20 12:30:26 -0500)

Hi; some of these commits seem to be missing Reviewed-by: tags;
for instance "ignore address_space_map is_write flag" got a
Reviewed-by from Darren Kenny, and that tag is visible in the
(second) copy of the email for the pullreq that you sent to the
list, but it isn't in the commit that's at the tag you name above,
and it's the commits in the git repo that end up in master, not
the patch emails sent to the list.

Also, are you in a position to get your GPG key signed by
anybody else? I appreciate that that's pretty tricky right
now given Covid, but if you have the opportunity at some point
that would be useful.

thanks
-- PMM


  parent reply	other threads:[~2021-01-22 15:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 17:44 [PULL 0/7] 2021-01-20 fuzzing patches Alexander Bulekov
2021-01-20 17:44 ` [PULL 1/7] fuzz: ignore address_space_map is_write flag Alexander Bulekov
2021-01-20 17:44 ` [PULL 2/7] fuzz: refine the ide/ahci fuzzer configs Alexander Bulekov
2021-01-20 17:44 ` [PULL 3/7] docs/fuzz: fix pre-meson path Alexander Bulekov
2021-01-20 17:44 ` [PULL 4/7] fuzz: log the arguments used to initialize QEMU Alexander Bulekov
2021-01-20 17:44 ` [PULL 5/7] fuzz: enable dynamic args for generic-fuzz configs Alexander Bulekov
2021-01-20 17:44 ` [PULL 6/7] docs/fuzz: add some information about OSS-Fuzz Alexander Bulekov
2021-01-20 17:44 ` [PULL 7/7] fuzz: add virtio-9p configurations for fuzzing Alexander Bulekov
2021-01-22 15:06 ` Peter Maydell [this message]
2021-01-25 19:09   ` [PULL 0/7] 2021-01-20 fuzzing patches Alexander Bulekov
  -- strict thread matches above, loose matches on Subject: below --
2021-01-20 17:35 Alexander Bulekov
2021-01-20 17:41 ` Alexander Bulekov

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='CAFEAcA8QNMiFe5p=-agvvnfFY_teMR3s-8AfT3OEa6GCK-Y=kg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alxndr@bu.edu \
    --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).