From: "Trilok Soni" <soni.trilok@gmail.com>
To: Carlos Aguiar <carlos.aguiar@indt.org.br>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 3/3] ARM: OMAP: Add menelaus chip info for N800
Date: Wed, 6 Jun 2007 13:04:24 +0530 [thread overview]
Message-ID: <5d5443650706060034o7ded97a7red9b02ca549a9d28@mail.gmail.com> (raw)
In-Reply-To: <46657635.7060902@indt.org.br>
On 6/5/07, Carlos Aguiar <carlos.aguiar@indt.org.br> wrote:
> ext Trilok Soni wrote:
> > Let me know if anybody tested this patch on N800. Thanx.
> >
> > ---Trilok Soni
> >
> > On 5/26/07, Trilok Soni <soni.trilok@gmail.com> wrote:
> >> n800 changes are compile tested only. Please test.
> >>
> >> --
> >> --Trilok Soni
> >>
> >>
> > _______________________________________________
> > Linux-omap-open-source mailing list
> > Linux-omap-open-source@linux.omap.com
> > http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> >
> Hi Tony and Trilok,
>
> I've tested the patches
> 0001-ARM-OMAP-Use-new-style-I2C-driver-for-Menelaus-chip.patch
> (http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/010100.html)
> and 0003-ARM-OMAP-Add-menelaus-chip-info-for-N800.patch
> (http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/010102.html)
>
> by applying it together over MMC multislot support patches series for
> N800 and looks fine (both slots with MMC, SD and SDHC cards).
>
> To test it, I'm using linux-omap tree, on commit
> 9a0fba3f2ca8e58a1465d6c3c18f9f334d054304). Today I'll test with most
> updated tree.
>
Thanx for the testing. Please share the result once you test it with
latest tree.
--
--Trilok Soni
next prev parent reply other threads:[~2007-06-06 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 8:29 [PATCH 3/3] ARM: OMAP: Add menelaus chip info for N800 Trilok Soni
2007-06-05 11:29 ` Trilok Soni
2007-06-05 14:41 ` Carlos Aguiar
2007-06-06 7:34 ` Trilok Soni [this message]
2007-06-06 19:47 ` Carlos Aguiar
2007-06-07 5:29 ` Trilok Soni
2007-06-11 13:31 ` Tony Lindgren
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=5d5443650706060034o7ded97a7red9b02ca549a9d28@mail.gmail.com \
--to=soni.trilok@gmail.com \
--cc=carlos.aguiar@indt.org.br \
--cc=linux-omap-open-source@linux.omap.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.