From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Otubo <eduardo.otubo@profitbricks.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/01] seccomp branch queue
Date: Mon, 20 Jun 2016 13:22:33 +0100 [thread overview]
Message-ID: <CAFEAcA89WbSHeiPPt_ytQHZ1bLekF5eueVy9g21GiyH3aSy0BA@mail.gmail.com> (raw)
In-Reply-To: <1466414253-21365-1-git-send-email-eduardo.otubo@profitbricks.com>
On 20 June 2016 at 10:17, Eduardo Otubo <eduardo.otubo@profitbricks.com> wrote:
> The following changes since commit 482b61844ae7c6df39df0b48ac90ffbc87bed7d2:
>
> Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20160617' into staging (2016-06-17 16:16:37 +0100)
>
> are available in the git repository at:
>
> git://github.com/otubo/qemu.git tags/pull-seccomp-20160620
>
> for you to fetch changes up to 3e684455032a748be261e5a2524147940af9b6d9:
>
> seccomp: Add support for ppc/ppc64 (2016-06-20 11:04:09 +0200)
>
> ----------------------------------------------------------------
> seccomp branch queue
>
> ----------------------------------------------------------------
> Michael Strosaker (1):
> seccomp: Add support for ppc/ppc64
Applied, thanks.
-- PMM
next prev parent reply other threads:[~2016-06-20 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 9:17 [Qemu-devel] [PULL 00/01] seccomp branch queue Eduardo Otubo
2016-06-20 9:17 ` [Qemu-devel] [PULL 01/01] seccomp: Add support for ppc/ppc64 Eduardo Otubo
2016-06-20 12:22 ` Peter Maydell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-01 12:08 [Qemu-devel] [PULL 00/01] seccomp branch queue Eduardo Otubo
2018-06-01 12:58 ` Peter Maydell
2017-06-22 8:33 Eduardo Otubo
2017-06-23 10:58 ` Peter Maydell
2017-06-23 17:11 ` Peter Maydell
2016-09-21 9:38 Eduardo Otubo
2016-09-22 13:23 ` Peter Maydell
2015-01-23 13:21 Eduardo Otubo
2015-01-23 17:09 ` 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=CAFEAcA89WbSHeiPPt_ytQHZ1bLekF5eueVy9g21GiyH3aSy0BA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=eduardo.otubo@profitbricks.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).