qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
	qemu-trivial@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Greg Kurz" <groug@kaod.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] travis.yml: Install libcap-dev for testing virito-9p
Date: Fri, 06 Sep 2019 13:05:36 +0100	[thread overview]
Message-ID: <87blvxzl2n.fsf@linaro.org> (raw)
In-Reply-To: <fc82454c-ee11-c7a3-cccb-eeb51df35897@redhat.com>


Thomas Huth <thuth@redhat.com> writes:

> On 05/09/2019 14.07, Greg Kurz wrote:
>> On Thu,  5 Sep 2019 13:33:46 +0200
>> Thomas Huth <thuth@redhat.com> wrote:
>>
>>> So far we were not testing virtio-9p in Travis yet, since we forgot to
>>> install libcap-devel. Do it now to get some more test coverage.
>>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>
>> Acked-by: Greg Kurz <groug@kaod.org>
>>
>> and
>>
>> Tested-by: Greg Kurz <groug@kaod.org>
>>
>> Whose tree is this going through BTW ?
>
> According to MAINTAINERS, .travis.yml is taken care of by Alex and Fam,
> so I hope they will pick this patch up. Otherwise, I think it could also
> go via trivial (now on CC: ), since it's just a one-liner.

Sure I'll grab it for the next iteration of testing/next - the queue is
quite full at the moment.


--
Alex Bennée


      reply	other threads:[~2019-09-06 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 11:33 [Qemu-devel] [PATCH] travis.yml: Install libcap-dev for testing virito-9p Thomas Huth
2019-09-05 11:41 ` Philippe Mathieu-Daudé
2019-09-05 12:07 ` Greg Kurz
2019-09-05 12:18   ` Greg Kurz
2019-09-06 11:22     ` Thomas Huth
2019-09-06 11:25   ` Thomas Huth
2019-09-06 12:05     ` Alex Bennée [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=87blvxzl2n.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=fam@euphon.net \
    --cc=groug@kaod.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.com \
    /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).