qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] Expand the building of qemu-user docker images
Date: Mon, 31 Oct 2016 21:39:14 +0800	[thread overview]
Message-ID: <20161031133914.GL30303@lemon> (raw)
In-Reply-To: <87d1igycfd.fsf@linaro.org>

On Mon, 10/31 11:40, Alex Bennée wrote:
> 
> Fam Zheng <famz@redhat.com> writes:
> 
> > On Fri, 10/28 17:33, Alex Bennée wrote:
> >> Hi Fam,
> >>
> >> These are a little bit of a work in progress so maybe not all ready to
> >> be taken yet although review would be welcome.
> >>
> >> This adds some tweaks to allow us to build the cross-arch debian
> >> images with direct make invocations and then see which images we can
> >> test against from the "make docker" help text. Now:
> >>
> >>   make docker-image-debian-stable-arm64
> >>
> >> Will do exactly as you expect. I can't get:
> >>
> >>   make docker-test-quick@debian-stable-arm64
> >>
> >> To work but I suspect this needs some fixing to the generated rules.
> >>
> >> Comments?
> >
> > Looks good, but what about binfmt_misc?
> 
> Currently the binfmt_misc check is done when the image is built (by the
> pre script). We could expand docker.py to check and use that?

I was just thinking that the real convenience only comes after the automated
setup of binfmt_misc (or a help text in "make docker" documentation).

What do you think?

Fam

      reply	other threads:[~2016-10-31 13:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 16:33 [Qemu-devel] [PATCH 0/6] Expand the building of qemu-user docker images Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 1/6] tests/docker/Makefile.include: fix diff-index call Alex Bennée
2016-10-31  2:19   ` Fam Zheng
2016-10-31 11:55     ` Alex Bennée
2016-11-01 10:02     ` Alex Bennée
2016-11-01 10:38       ` Fam Zheng
2016-11-01 11:41         ` Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 2/6] tests/docker/test-user: a simple linux-user test Alex Bennée
2016-10-31  2:20   ` Fam Zheng
2016-10-28 16:33 ` [Qemu-devel] [PATCH 3/6] tests/docker: add optional libs to travis.docker Alex Bennée
2016-10-31  2:23   ` Fam Zheng
2016-10-28 16:33 ` [Qemu-devel] [PATCH 4/6] tests/docker/Makefile: Add a rule for Debian user images Alex Bennée
2016-10-28 16:33 ` [Qemu-devel] [PATCH 5/6] tests/docker/docker.py: expand images command Alex Bennée
2016-10-31  2:28   ` Fam Zheng
2016-10-28 16:33 ` [Qemu-devel] [PATCH 6/6] tests/docker/Makefile.include: expand docker help text Alex Bennée
2016-10-31  2:34   ` Fam Zheng
2016-10-31  2:41 ` [Qemu-devel] [PATCH 0/6] Expand the building of qemu-user docker images Fam Zheng
2016-10-31 11:40   ` Alex Bennée
2016-10-31 13:39     ` Fam Zheng [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=20161031133914.GL30303@lemon \
    --to=famz@redhat.com \
    --cc=alex.bennee@linaro.org \
    --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).