From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: 2.6.16-omap2 tagged & patches available
Date: Tue, 04 Apr 2006 13:57:27 -0700 [thread overview]
Message-ID: <4432DDB7.7080204@am.sony.com> (raw)
In-Reply-To: <20060404144930.GD15266@atomide.com>
Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [060403 13:46]:
>> Hi all,
>>
>> Turns out the MMC bug on H2 and H3 was related to the recent clock id
>> usgage :)
>>
>> I've tagged 2.6.16-omap1 and posted a patch to the usual location:
>>
>> http://www.muru.com/linux/omap/
>
> I generated a quick 2.6.16-omap2 with the 1510 USB host patch in it.
>
Sorry, seems to be bad. Nothing inside...
$ quilt push
Applying osk-support/patch-2.6.16-omap2
patch: **** Only garbage was found in the patch input.
Patch osk-support/patch-2.6.16-omap2 does not apply (enforce with -f)
next prev parent reply other threads:[~2006-04-04 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 20:44 2.6.16-omap1 tagged & patches available Tony Lindgren
2006-04-04 14:49 ` 2.6.16-omap2 " Tony Lindgren
2006-04-04 20:57 ` Geoff Levand [this message]
2006-04-04 21:22 ` Tony Lindgren
2006-04-04 21:44 ` Geoff Levand
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=4432DDB7.7080204@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.com \
/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