From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Kernel recipes with broken PRs now
Date: Sun, 24 May 2009 15:04:50 +0200 [thread overview]
Message-ID: <gvbgli$1iu$1@ger.gmane.org> (raw)
In-Reply-To: <1243168060.4226.161.camel@lenovo.internal.reciva.com>
On 24-05-09 14:27, Phil Blundell wrote:
> It seems fairly clear that, as the originator of the patch in question,
> the onus is on you to minimise any resulting damage to other users.
I'm gradually fixing kernel as I encounter them, but since I don't have
access to all hardware present in OE, or computing power to test all
toolchain permutations needed to build all kernels (e.g. kernels
requiring gcc 2.93.3), I am currently limiting that effort to kernel I
can actually test.
Furthermore, only kernel actually used by machines present in OE can get
fixed, we have a number of kernels that have recipes, but no machines
using them.
regards,
Koen
next prev parent reply other threads:[~2009-05-24 13:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 21:31 Kernel recipes with broken PRs now Tom Rini
2009-05-22 22:27 ` Andrea Adami
2009-05-23 5:22 ` Koen Kooi
2009-05-23 5:31 ` Tom Rini
2009-05-30 19:13 ` Tom Rini
2009-05-30 21:13 ` Koen Kooi
2009-05-30 22:27 ` Tom Rini
2009-05-31 7:36 ` Koen Kooi
2009-05-23 13:06 ` Leon Woestenberg
2009-05-23 16:23 ` Phil Blundell
2009-05-23 22:25 ` Leon Woestenberg
2009-05-24 8:23 ` Koen Kooi
2009-05-24 9:23 ` Phil Blundell
2009-05-24 11:37 ` Koen Kooi
2009-05-24 12:27 ` Phil Blundell
2009-05-24 13:04 ` Koen Kooi [this message]
2009-05-24 16:51 ` Phil Blundell
2009-05-24 21:45 ` Leon Woestenberg
2009-05-24 18:49 ` Marcin Juszkiewicz
2009-05-30 19:16 ` Tom Rini
2009-05-30 21:13 ` Koen Kooi
2009-05-30 21:33 ` Tom Rini
2009-05-30 22:16 ` Otavio Salvador
2009-05-30 22:28 ` Tom Rini
2009-05-30 23:04 ` Phil Blundell
2009-05-31 0:49 ` Otavio Salvador
2009-05-31 10:00 ` Phil Blundell
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='gvbgli$1iu$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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.