xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 6/8] ts-kernel-build: Include dtbs in dist file
Date: Tue, 6 Oct 2015 14:24:31 +0100	[thread overview]
Message-ID: <1444137871.5302.168.camel@citrix.com> (raw)
In-Reply-To: <1444062570.5302.30.camel@citrix.com>

On Mon, 2015-10-05 at 17:29 +0100, Ian Campbell wrote:
> On Mon, 2015-10-05 at 17:22 +0100, Ian Jackson wrote:
> > Ian Campbell writes ("[PATCH OSSTEST 6/8] ts-kernel-build: Include dtbs
> > in dist file"):
> > > These are installed to $(INSTALL_PATH)/dtbs/$(KERNEL_RELEASE) where
> > > $(INSTALL_PATH) defaults to /boot but we override it to our staging
> > > /boot.
> > 
> > Thanks for the detailed explanation.
> > 
> > Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> > 
> > > -	make $makeflags INSTALL_MOD_PATH=$builddir/dist
> > > modules_install
> > > +	make $makeflags \\
> > > +		INSTALL_PATH=$builddir/dist/boot \\
> > > +		INSTALL_MOD_PATH=$builddir/dist modules_install \\
> > > +		$dtbs_install
> > 
> > I tripped over the formatting here.  It would be nicer to put
> > `modules_install' on the next line, to avoid hiding it in
> > INSTALL_BLAH=.
> 
> I did it that way because INSTALL_MOD_PATH is the variable which controls
> where modules_install puts things, so they are in some sense related.
> 
> Next line is fine too, or I could move it to first on the line it is on
> now?

I went with:

+       make $makeflags \\
+               INSTALL_PATH=$builddir/dist/boot \\
+               INSTALL_MOD_PATH=$builddir/dist \\
+               modules_install $dtbs_install

which did seem clearer.

Ian.

  reply	other threads:[~2015-10-06 13:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  9:25 [PATCH OSSTEST 0/8] Use the DTB provided by the kernel we are trying to boot Ian Campbell
2015-10-02  9:26 ` [PATCH OSSTEST 1/8] Osstest: Add %arch_debian2linux (and inverse) Ian Campbell
2015-10-05 16:18   ` Ian Jackson
2015-10-02  9:26 ` [PATCH OSSTEST 2/8] ts-kernel-build: Introduce global $parms Ian Campbell
2015-10-05 16:18   ` Ian Jackson
2015-10-02  9:26 ` [PATCH OSSTEST 3/8] ts-kernel-build: Refactor $archparams::DefConfig selection Ian Campbell
2015-10-05 16:19   ` Ian Jackson
2015-10-02  9:26 ` [PATCH OSSTEST 4/8] ts-kernel-build: Refactor $archparams KernelImage handling Ian Campbell
2015-10-05 16:19   ` Ian Jackson
2015-10-02  9:26 ` [PATCH OSSTEST 5/8] ts-kernel-build: Add arm64 support Ian Campbell
2015-10-05 16:20   ` Ian Jackson
2015-10-05 16:28     ` Ian Campbell
2015-10-06 13:35       ` Ian Jackson
2015-10-02  9:26 ` [PATCH OSSTEST 6/8] ts-kernel-build: Include dtbs in dist file Ian Campbell
2015-10-05 16:22   ` Ian Jackson
2015-10-05 16:29     ` Ian Campbell
2015-10-06 13:24       ` Ian Campbell [this message]
2015-10-06 13:36         ` Ian Jackson
2015-10-06 13:36       ` Ian Jackson
2015-10-02  9:26 ` [PATCH OSSTEST 7/8] Debian: Enable interpolation in uboot_scr_load_dtb here doc Ian Campbell
2015-10-05 16:24   ` Ian Jackson
2015-10-05 16:30     ` Ian Campbell
2015-10-02  9:26 ` [PATCH OSSTEST 8/8] Debian: Use dtbs from kernel dist when booting that kernel Ian Campbell
2015-10-05 16:29   ` Ian Jackson

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=1444137871.5302.168.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).