[Qemu-devel] [PULL 00/01] seccomp branch queue

Eduardo Otubo posted 1 patch 129 weeks ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20170622083336.19479-1-otubo@redhat.com
Test FreeBSD passed
Test checkpatch passed
Test docker passed
Test s390x passed
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

[Qemu-devel] [PULL 00/01] seccomp branch queue

Posted by Eduardo Otubo 129 weeks ago
The following changes since commit 8dfaf23ae1f2273a9730a9b309cc8471269bb524:

  tcg/tci: fix tcg-interpreter build (2017-06-20 18:39:15 +0100)

are available in the git repository at:

  https://github.com/otubo/qemu.git tags/pull-seccomp-20170622

for you to fetch changes up to 064983cb0a18c5adc4ec791c00792f74ebf50ca4:

  MAINTAINERS: seccomp: change email contact for Eduardo Otubo (2017-06-22 09:58:00 +0200)

----------------------------------------------------------------
seccomp branch queue

----------------------------------------------------------------
Eduardo Otubo (1):
      MAINTAINERS: seccomp: change email contact for Eduardo Otubo

 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.9.4


Re: [Qemu-devel] [PULL 00/01] seccomp branch queue

Posted by Peter Maydell 128 weeks ago
On 22 June 2017 at 09:33, Eduardo Otubo <otubo@redhat.com> wrote:
> The following changes since commit 8dfaf23ae1f2273a9730a9b309cc8471269bb524:
>
>   tcg/tci: fix tcg-interpreter build (2017-06-20 18:39:15 +0100)
>
> are available in the git repository at:
>
>   https://github.com/otubo/qemu.git tags/pull-seccomp-20170622
>
> for you to fetch changes up to 064983cb0a18c5adc4ec791c00792f74ebf50ca4:
>
>   MAINTAINERS: seccomp: change email contact for Eduardo Otubo (2017-06-22 09:58:00 +0200)
>
> ----------------------------------------------------------------
> seccomp branch queue
>
> ----------------------------------------------------------------
> Eduardo Otubo (1):
>       MAINTAINERS: seccomp: change email contact for Eduardo Otubo

Hi Eduardo -- this pullreq isn't signed with the gpg key I have
on record for you, and the keyservers say the key it is signed
with hasn't been signed by anybody else...

thanks
-- PMM