From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device
Date: Wed, 10 Jun 2015 08:48:38 +0200 [thread overview]
Message-ID: <20150610064838.GB10886@amd> (raw)
In-Reply-To: <201506100627.37959.marex@denx.de>
On Wed 2015-06-10 06:27:37, Marek Vasut wrote:
> On Tuesday, June 09, 2015 at 06:28:29 PM, Pali Roh?r wrote:
> > On Monday 08 June 2015 23:24:18 Paul Kocialkowski wrote:
> > > I would be very glad to see board maintainers give a go
> > > at the changeset before it gets merged, especially on devices like
> > > the Nokia RX-51 (N900) where some specific adaptation was needed.
> >
> > So U-Boot is broken since e11c6c279d823dc0d2f470c5c2e3c0a9854a640f (see
> > other email thread
>
> Would be nice if you added a link to the thread in some mail archive ...
>
> > ). Until somebody fix that broken commit, I cannot
> > test your new patches in qemu or on (real) Nokia N900.
>
> What about you fixing it ? ;-)
Traditionally, regressions are fixed by whoever caused then, not
whoever was patient enough to bisect them...
But in this case, fix is already available, so that is moot.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-06-10 6:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 17:03 [U-Boot] [RFC] [PATCH] omap-common: Common boot code OMAP3 support and cleanup Paul Kocialkowski
2015-06-03 17:03 ` [U-Boot] " Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 1/8] omap-common: Common boot code OMAP3 support and cleanup Paul Kocialkowski
2015-06-09 14:48 ` Pali Rohár
2015-06-08 21:24 ` [U-Boot] [PATCH v2 2/8] omap: SPL boot devices cleanup and completion Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 3/8] omap-common: Boot device define instead of hardcoded value Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 4/8] siemens-am33x-common: Hardcoded value instead of non-included define Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 5/8] omap-common: SYS_BOOT-based fallback boot device selection for peripheral boot Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 6/8] omap3: Definitions for SYS_BOOT-based fallback boot device selection Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 7/8] omap4: " Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 8/8] omap5: " Paul Kocialkowski
2015-06-09 16:28 ` [U-Boot] [PATCH v2 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Pali Rohár
2015-06-09 18:34 ` Pali Rohár
2015-06-10 9:54 ` Paul Kocialkowski
2015-06-10 10:34 ` Pali Rohár
2015-06-10 10:42 ` Pali Rohár
2015-06-10 10:58 ` Paul Kocialkowski
2015-06-10 11:35 ` Pali Rohár
2015-06-12 11:32 ` Paul Kocialkowski
2015-06-12 11:56 ` Pali Rohár
2015-06-12 13:01 ` Paul Kocialkowski
2015-06-12 13:10 ` Pali Rohár
2015-06-12 13:54 ` Paul Kocialkowski
2015-06-10 4:27 ` Marek Vasut
2015-06-10 6:08 ` Pali Rohár
2015-06-10 6:48 ` Pavel Machek [this message]
2015-06-10 7:47 ` Pali Rohár
2015-06-10 7:45 ` Pali Rohár
2015-06-10 8:47 ` Marek Vasut
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=20150610064838.GB10886@amd \
--to=pavel@denx.de \
--cc=u-boot@lists.denx.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