mbox

[PULL,00/01] seccomp: exit if seccomp_init() fails

Message ID 1387565447-24241-1-git-send-email-otubo@linux.vnet.ibm.com
State New
Headers show

Pull-request

git://github.com/otubo/qemu.git seccomp

Message

Eduardo Otubo Dec. 20, 2013, 6:50 p.m. UTC 
The following changes since commit 2a13f991123fa16841e6d94b02a9cc2c76d91725:

  seccomp: exit if seccomp_init() fails (2013-12-20 16:38:29 -0200)

are available in the git repository at:
  git://github.com/otubo/qemu.git seccomp

Corey Bryant (1):
  seccomp: exit if seccomp_init() fails

 qemu-seccomp.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

Comments

Markus Armbruster Jan. 7, 2014, 4:30 p.m. UTC | #1 
Eduardo Otubo <otubo@linux.vnet.ibm.com> writes:

> The following changes since commit 2a13f991123fa16841e6d94b02a9cc2c76d91725:
>
>   seccomp: exit if seccomp_init() fails (2013-12-20 16:38:29 -0200)
>
> are available in the git repository at:
>   git://github.com/otubo/qemu.git seccomp

It's been almost three weeks.  What's holding this up?
Paul Moore Jan. 9, 2014, 9:35 p.m. UTC | #2 
On Tuesday, January 07, 2014 05:30:32 PM Markus Armbruster wrote:
> Eduardo Otubo <otubo@linux.vnet.ibm.com> writes:
> > The following changes since commit 
2a13f991123fa16841e6d94b02a9cc2c76d91725:
> >   seccomp: exit if seccomp_init() fails (2013-12-20 16:38:29 -0200)
> > 
> > are available in the git repository at:
> >   git://github.com/otubo/qemu.git seccomp
> 
> It's been almost three weeks.  What's holding this up?

Agreed, this is silly, especially for such a small and obvious fix.