qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair.francis@xilinx.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alistair Francis <alistair.francis@xilinx.com>,
	Edgar Iglesias <edgar.iglesias@xilinx.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/5] Expose the secure and virt properties to the
Date: Thu, 7 Sep 2017 09:48:51 -0700	[thread overview]
Message-ID: <CAKmqyKOqOJJceCf-wMjZTMQCHDjHWGWT4JAdsqERVXeNtTP6dw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_0FyFFqJ2GOtUw5CPBKTj1YR9ykroyL-7WCYfbgR0hAg@mail.gmail.com>

On Thu, Sep 7, 2017 at 9:33 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 7 September 2017 at 17:29, Alistair Francis
> <alistair.francis@xilinx.com> wrote:
>> It looks like patch 1 and 3 still didn't make it through. I see them
>> leaving the corporate network and going through to my personal email.
>>
>> Can anyone see anything on the QEMU mail server side? Any logs might
>> help me push IT to investigate.
>
> Unfortunately we don't really have much visibility into what
> the mail server is doing, because it's run by nongnu.org.
> It does seem to have a habit of occasionally eating patches
> (maybe it thinks they're spam or something).

Hmmm... I'm not sure how to look into this then, as I can see the
patches going through to my personal email address, so it's hard to
place the blame on the Xilinx mail server.

Do you want me to try sending out patches 1 and 3 again?

Thanks,
Alistair

>
> thanks
> -- PMM
>

  reply	other threads:[~2017-09-07 16:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 23:34 [Qemu-devel] [PATCH v2 0/5] Expose the secure and virt properties to the Alistair Francis
2017-08-31 23:34 ` [Qemu-devel] [PATCH v2 4/5] xlnx-zcu102: Add a machine level virtualization property Alistair Francis
2017-08-31 23:34 ` [Qemu-devel] [PATCH v2 5/5] xlnx-zcu102: Mark the EP108 machine as deprecated Alistair Francis
2017-09-07 12:51 ` [Qemu-devel] [PATCH v2 0/5] Expose the secure and virt properties to the Peter Maydell
2017-09-07 16:01   ` Alistair Francis
2017-09-07 16:29     ` Alistair Francis
2017-09-07 16:33       ` Peter Maydell
2017-09-07 16:48         ` Alistair Francis [this message]
2017-09-07 18:06           ` Richard Henderson
2017-09-07 18:08             ` Peter Maydell
2017-09-07 18:13               ` Alistair Francis
2017-09-07 15:57 ` [Qemu-devel] [PATCH Resend v2 2/5] xlnx-zcu102: Manually create the machines Alistair Francis
2017-09-07 21:35 ` [Qemu-devel] [PATCH Resend v2 0/5] Expose the secure and virt properties to the Edgar E. Iglesias
2017-09-07 21:44   ` Alistair Francis
2017-09-14 12:30     ` Peter Maydell

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=CAKmqyKOqOJJceCf-wMjZTMQCHDjHWGWT4JAdsqERVXeNtTP6dw@mail.gmail.com \
    --to=alistair.francis@xilinx.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).