All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milton Miller <miltonm@bga.com>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC,PATCH] scripts/package: add powerpc images to tarball
Date: Fri, 25 Jul 2008 22:59:06 -0500	[thread overview]
Message-ID: <b15cc94f988df8d269ad40fafcd911cb@bga.com> (raw)
In-Reply-To: <200807251111.26673.jk@ozlabs.org>


On Jul 24, 2008, at 8:11 PM, Jeremy Kerr wrote:

> Milton,
>
>> Yes.  How about all dtbImage, zImage, cuboot, treeboot, etc
>> that are newer than vmlinux?
>
> The existing arch code doesn't do any checks for timestamps, perhaps
> this would be better implemented as an arch-independent change?

The problem is some people might want to add intermediate files that are
younger than vmlinux (eg .config).  We know our boot-image should be
newer.  But I don't know how one would express the expected ages.

The reason I suggested the check was to eliminate images that are not
in the current config.  I figured a test for relative file age could
be done in the for loop -- possibly replace shell wildcard with
find arch/$(ARCH)/boot/{zImage*,dtbImage*,uImage*,cuImage*,treeboot*}
-newer vmlinux -print.

> (but would you like me to add treeboot and cuboot?)

I don't see why we should prefer the workstations and servers over the
embedded boards.  zImage is just a link to the first boot image, but
one can build a multiple formats and the order is somewhat arbitrary.
So I see it as fairness.  Otherwise, there are a few other platforms
that are "user" based vs embedded (like efkia, no?).

milton

  reply	other threads:[~2008-07-26  3:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24  8:17 [RFC,PATCH] scripts/package: add powerpc images to tarball Jeremy Kerr
2008-07-25  1:08 ` Milton Miller
2008-07-25  1:11   ` Jeremy Kerr
2008-07-26  3:59     ` Milton Miller [this message]
2008-07-26  4:55   ` Grant Likely
2008-07-26  4:55     ` Grant Likely
2008-07-26 17:20     ` Milton Miller
2008-07-26 17:53       ` Grant Likely
2008-07-28 16:34         ` T Ziomek
2008-07-28 16:34           ` T Ziomek
2008-07-28 16:49           ` Grant Likely
2008-07-28 16:49             ` Grant Likely

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=b15cc94f988df8d269ad40fafcd911cb@bga.com \
    --to=miltonm@bga.com \
    --cc=jk@ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.