From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Otubo <otubo@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/1] seccomp branch queue
Date: Tue, 15 Sep 2020 13:48:13 +0100 [thread overview]
Message-ID: <CAFEAcA8J+8hMSQE36wYc6QMdtdMg-_ZSYbNKca1UQ9u2epWCQg@mail.gmail.com> (raw)
In-Reply-To: <20200915110155.15362-1-otubo@redhat.com>
On Tue, 15 Sep 2020 at 12:02, Eduardo Otubo <otubo@redhat.com> wrote:
>
> The following changes since commit 2d2c73d0e3d504a61f868e46e6abd5643f38091b:
>
> Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20200914-1' into staging (2020-09-14 16:03:08 +0100)
>
> are available in the Git repository at:
>
> git://github.com/otubo/qemu.git tags/pull-seccomp-20200915
>
> for you to fetch changes up to e474e3aacf4276eb0781d11c45e2fab996f9dc56:
>
> seccomp: fix killing of whole process instead of thread (2020-09-15 12:56:26 +0200)
>
> ----------------------------------------------------------------
> pull-seccomp-20200915
>
> ----------------------------------------------------------------
> Daniel P. Berrangé (1):
> seccomp: fix killing of whole process instead of thread
>
> qemu-seccomp.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Strictly speaking patches you send in a pullreq should have your
signed-off-by, but I figured in this case the acked-by was
close enough and it's only one patch.
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/5.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2020-09-15 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 11:01 [PULL 0/1] seccomp branch queue Eduardo Otubo
2020-09-15 11:01 ` [PULL 1/1] seccomp: fix killing of whole process instead of thread Eduardo Otubo
2020-09-15 12:48 ` Peter Maydell [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=CAFEAcA8J+8hMSQE36wYc6QMdtdMg-_ZSYbNKca1UQ9u2epWCQg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=otubo@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).