From: Rouven Czerwinski <rouven@czerwinskis.de>
To: distrokit@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [DistroKit] [PATCH 00/14] Barebox Update and Cleanup
Date: Mon, 04 Nov 2019 14:18:45 +0100 [thread overview]
Message-ID: <87v9rzeq4q.fsf@czerwinskis.de> (raw)
In-Reply-To: <20191104100942.nr2npbfaayk3r3mb@pengutronix.de>
Roland Hieber <rhi@pengutronix.de> writes:
> On Sat, Nov 02, 2019 at 10:15:31AM +0100, Robert Schwebel wrote:
>> Hi,
>>
>> On Tue, Oct 29, 2019 at 04:42:34PM +0100, Robert Schwebel wrote:
>> > On Tue, Oct 29, 2019 at 12:28:47PM +0100, Michael Olbrich wrote:
>> > > Here are some updates for the different barebox packages. It's a version
>> > > bump to the latest release from Ahmad and various cleanups.
>> > > Most of this is basically synchronization with the latest upstream
>> > > template. This also includes a switch to out-of-tree builds, which is
>> > > useful in combination with local-src.
>> > > And there are some fixes for the package clean targets.
>> >
>> > Looks good, testing in -next.
>>
>> It failed on the beaglebone, could you please check?
>> http://jenkins.hi.pengutronix.de/job/ptxdist-bsps/job/DistroKit/job/labgrid-DistroKit-next-beaglebone/129/console
>
> [...]
> 20:27:12 Aborted by Rouven Czerwinski
> [...]
>
> The next build now looks like the builds before that.
The patches lost the default boot target for the bootloader on
beaglebone, its trying to "boot net" instead of using the eMMC.
No need to continue a test run which won't work.
- rcz
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2019-11-04 13:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 11:28 Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 01/14] v7a: barebox-common: modify oldconfig to affect all bareboxes Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 02/14] v7a: barebox-common: add clean target that affects " Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 03/14] v7a: barebox: version bump 2019.08.1 → 2019.10.0 Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 04/14] barebox-vexpress: sync with latest barebox template Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 05/14] barebox-mx6: " Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 06/14] barebox-rpi2: " Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 07/14] barebox-am335x-mlo: " Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 08/14] barebox-am335x: " Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 09/14] barebox-common: " Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 10/14] barebox-vexpress: remove installed files Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 11/14] barebox-rpi2: don't add a suffix to the images Michael Olbrich
2019-10-29 11:28 ` [DistroKit] [PATCH 12/14] barebox-am335x-mlo: actually remove images during 'clean' Michael Olbrich
2019-10-29 11:29 ` [DistroKit] [PATCH 13/14] barebox-am335x: " Michael Olbrich
2019-10-29 11:29 ` [DistroKit] [PATCH 14/14] barebox-mx6: " Michael Olbrich
2019-10-29 15:42 ` [DistroKit] [PATCH 00/14] Barebox Update and Cleanup Robert Schwebel
2019-11-02 9:15 ` Robert Schwebel
2019-11-04 10:09 ` Roland Hieber
2019-11-04 13:18 ` Rouven Czerwinski [this message]
2019-11-04 21:16 ` Michael Olbrich
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=87v9rzeq4q.fsf@czerwinskis.de \
--to=rouven@czerwinskis.de \
--cc=distrokit@pengutronix.de \
--cc=m.olbrich@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