From: Tony Lindgren <tony@atomide.com>
To: Govindraj <govindraj.ti@gmail.com>
Cc: Luke-Jr <luke@dashjr.org>, "Govindraj.R" <govindraj.raja@ti.com>,
linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH v3] serial: Add OMAP high-speed UART driver
Date: Wed, 7 Jul 2010 15:02:42 +0300 [thread overview]
Message-ID: <20100707120241.GN1920@atomide.com> (raw)
In-Reply-To: <AANLkTinod9geJbbfdOIhB465qi6xHqfH-1vL048Bc3fa@mail.gmail.com>
* Govindraj <govindraj.ti@gmail.com> [100608 09:24]:
> On Mon, Jun 7, 2010 at 9:45 PM, Luke-Jr <luke@dashjr.org> wrote:
> > On Monday 07 June 2010 08:28:51 am Govindraj wrote:
> >> Link:
> >> http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summa
> >> ry
> >>
> >> Branch:
> >> pm-wip/uart
> >
> > This branch doesn't appear to have omap-serial.c at all...
> >
> >> If you are trying to use with any client device connected to uart
> >> then we need to ensure the client driver speaks to omap-serial
> >> dev entries.
> >
>
> You need apply the driver patch on top of this branch.
>
> [PATCH v3] serial: Add OMAP high-speed UART driver.
Do we still have a dependency to pm-wip/uart branch? Can you please
check if you can rebase all these patches on top of linux-omap for-next
branch?
Regards,
Tony
next prev parent reply other threads:[~2010-07-07 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 13:54 [PATCH v3] serial: Add OMAP high-speed UART driver Govindraj.R
2010-06-05 18:48 ` Luke-Jr
2010-06-07 6:49 ` Govindraj
2010-06-07 13:09 ` Luke-Jr
2010-06-07 13:28 ` Govindraj
2010-06-07 16:15 ` Luke-Jr
2010-06-08 6:30 ` Govindraj
2010-07-07 12:02 ` Tony Lindgren [this message]
2010-07-07 12:22 ` Govindraj
2010-08-09 19:29 ` Kevin Hilman
2010-08-11 13:10 ` Govindraj
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=20100707120241.GN1920@atomide.com \
--to=tony@atomide.com \
--cc=govindraj.raja@ti.com \
--cc=govindraj.ti@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luke@dashjr.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 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.