From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Robert Schwebel <r.schwebel@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] Kernel: never provide a development prebuild package
Date: Tue, 21 Jan 2014 14:29:29 +0100 [thread overview]
Message-ID: <201401211429.29200.jbe@pengutronix.de> (raw)
In-Reply-To: <20140121120044.GJ12605@pengutronix.de>
On Tuesday 21 January 2014 13:00:44 Robert Schwebel wrote:
> [...]
> The idea of the devpkg mechanism is to build everything beforehand. A
> standard usecase is that one team prepares a system and another one does
> already care about the application. So it would be helpful to have also
> the kernel pre-built.
>
> Can you elaborate what kind of issue you have seen?
The main kernel images (in my case uimage) are not part of the archive and that
is why the targetinstall stage fails later on.
This patch was generated and sent after talking to Michael.
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-01-21 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 11:59 Juergen Beisert
2014-01-21 12:00 ` Robert Schwebel
2014-01-21 13:22 ` Michael Olbrich
2014-01-21 13:29 ` Juergen Beisert [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=201401211429.29200.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=r.schwebel@pengutronix.de \
/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