public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: linux-omap-open-source@linux.omap.com,
	Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Subject: Re: [PATCH 0/3] OMAP MMU framework patches
Date: Wed, 21 Feb 2007 23:44:29 -0800	[thread overview]
Message-ID: <20070222074428.GB8116@atomide.com> (raw)
In-Reply-To: <5d5443650702212126m20d16900p3e5e3c8c30b77fa4@mail.gmail.com>

* Trilok Soni <soni.trilok@gmail.com> [070221 21:27]:
> On 2/20/07, Trilok Soni <soni.trilok@gmail.com> wrote:
> >
> >>
> >> For reference I've attached the patch for omap1, but I havn't had
> >> enough time to test this with N770, probably something is still
> >> missing.
> >
> >Thanx. Let's see what Tony suggest. If he wants to me to integrate all
> >above changes and re-produce the patches OR submit them as incremental
> >patches.
> >
> 
> OK. I have decided to re-submit this patchset with new changes as
> suggested by Doyu-San along with his patch changes for OMAP1. I will
> do this by probably end of this week. BTW, changes for mmu fwk to
> built as module are already finished in my git tree.

OK, that sounds good to me and should take care of the omap1 testing
then.

Tony

  reply	other threads:[~2007-02-22  7:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20  6:51 [PATCH 0/3] OMAP MMU framework patches Trilok Soni
2007-02-20  7:54 ` Hiroshi DOYU
2007-02-20  8:21   ` Trilok Soni
2007-02-22  5:26     ` Trilok Soni
2007-02-22  7:44       ` Tony Lindgren [this message]
     [not found] <3B6D69C3A9EBCA4BA5DA60D913027429636DBF@dlee13.ent.ti.com>
2007-03-05 19:31 ` Zhang, Jian
2007-03-06  5:45   ` Trilok Soni
2007-03-06  9:41     ` Hiroshi DOYU

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=20070222074428.GB8116@atomide.com \
    --to=tony@atomide.com \
    --cc=Hiroshi.DOYU@nokia.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=soni.trilok@gmail.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