All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-omap-open-source@linux.omap.com"
	<linux-omap-open-source@linux.omap.com>
Subject: Re: Git tree tagged & updated 2.6.19-omap1 patch posted
Date: Fri, 22 Dec 2006 01:58:59 +0000 (GMT)	[thread overview]
Message-ID: <17313541.368131166752739331.JavaMail.weblogic@ep_ml29> (raw)

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

Thank you,

I'm waiting the linux-2.6.19-omap1. :)

With updated. Do you test the kernel-2.6.20-rc1?

Actually I downloaded the latest kernel from kernel.org.

But it can't boot since some ioremap failed with "remap_area_pte: page already exists" (remap_area_pte()) in arch/arm/mm/ioremap.c

Is there anyone who have same experience?

Thank you,
Kyungmin Park


------- Original Message -------
Sender : Tony Lindgren<tony@atomide.com> 
Date   : Dec 22, 2006 10:47
Title  : Git tree tagged & updated 2.6.19-omap1 patch posted

Hi all,

I've just tagged 2.6.19-omap1 and posted the related patch to
muru.com [1] and it should be shortly available at [2].

I've also updated the tree to 2.6.20-rc1. Things may be broken
because of the workqueue changes..

Regards,

Tony

[1] http://www.muru.com/linux/omap/
[2] http://linux.omap.com/pub/patches/www.muru.com.mirror/
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source



[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2006-12-22  1:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22  1:58 Kyungmin Park [this message]
2006-12-22  2:10 ` Git tree tagged & updated 2.6.19-omap1 patch posted Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2006-12-22  5:44 Kyungmin Park
2006-12-22  1:47 Tony Lindgren
2006-12-22 10:16 ` Dirk Behme

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=17313541.368131166752739331.JavaMail.weblogic@ep_ml29 \
    --to=kyungmin.park@samsung.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 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.