From: Tony Lindgren <tony@atomide.com>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: "linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>
Subject: Re: v2.6.28-omap1 tagged, some bugs remain
Date: Mon, 12 Jan 2009 18:15:20 +0200 [thread overview]
Message-ID: <20090112161514.GP9373@atomide.com> (raw)
In-Reply-To: <B5CEECBB-9939-46B9-BEDB-D8D9879DB63E@student.utwente.nl>
* Koen Kooi <k.kooi@student.utwente.nl> [090112 17:40]:
>
> Op 12 jan 2009, om 15:50 heeft Tony Lindgren het volgende geschreven:
>
>> Hi all,
>>
>> I've just tagged v2.6.28-omap1, and looks like we might want to also
>> do v2.6.28-omap2 as there are few annoying bugs remaining:
>>
>> - According to Jarkko Nikula, ASoC does not currently work because of
>> some recent clock changes.
>
> Confirmed on omap3evm.
Thanks, can you try to git-bisect the breaking commit?
>> - MMC seems to be broken for omap1, Ladislav Michl might have a patch
>> coming up for that.
>>
>> - I2C is broken for 2430 according to Kainan Cha.
And also musb might require some patches, pending comments from Felipe.
>> Also looks like source.mvista.com is down, so please use the
>> kernel.org
>> tree.
>>
>> Regards,
>>
>> Tony
next prev parent reply other threads:[~2009-01-12 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 14:50 v2.6.28-omap1 tagged, some bugs remain Tony Lindgren
2009-01-12 15:39 ` Koen Kooi
2009-01-12 16:15 ` Tony Lindgren [this message]
2009-01-13 7:08 ` Jarkko Nikula
2009-01-13 15:37 ` Anuj Aggarwal
2009-01-15 14:53 ` Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2009-01-14 8:27 Eero Nurkkala
2009-01-14 15:28 ` Tony Lindgren
2009-01-19 7:54 ` Jarkko Nikula
2009-01-23 0:02 ` Tony Lindgren
2009-01-23 7:49 ` Jarkko Nikula
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=20090112161514.GP9373@atomide.com \
--to=tony@atomide.com \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox