public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@nokia.com>
To: "ext Munegowda, Keshava" <keshava_mgowda@ti.com>
Cc: "Balbi Felipe (Nokia-MS/Helsinki)" <felipe.balbi@nokia.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Gadiyar, Anand" <gadiyar@ti.com>
Subject: Re: [PATCH 5/6] usb: ohci: don't hard-code TLL channel count
Date: Thu, 19 Aug 2010 10:23:12 +0300	[thread overview]
Message-ID: <20100819072312.GV4385@nokia.com> (raw)
In-Reply-To: <0680EC522D0CC943BC586913CF3768C003B39A33E9@dbde02.ent.ti.com>

Hi,

please teach your mailer to break the lines at 80 characters.

On Thu, Aug 19, 2010 at 08:26:06AM +0200, ext Munegowda, Keshava wrote:
>The function ohci_omap3_tll_config will be used with different tll 
>channel count in case of OMAP4 support soon, hence this change is 
>required.  We have removed only the hardcoded values used by this 
>function.

ok then. That's what I expected to hear.

-- 
balbi

DefectiveByDesign.org

  reply	other threads:[~2010-08-19  7:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  2:55 [PATCH 0/5] usb: omap: prepare for OMAP4 EHCI and OHCI support Keshava Munegowda
     [not found] ` <1282100145-27485-1-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18  2:55   ` [PATCH 1/5] usb: ehci: omap: Update clock names to be same across OMAP3 and OMAP4 Keshava Munegowda
2010-08-18  2:55     ` [PATCH 2/5] usb: ehci: don't hard-code TLL channel count Keshava Munegowda
     [not found]       ` <1282100145-27485-3-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18  2:55         ` [PATCH 3/5] usb: ehci: relocate PHY reset code Keshava Munegowda
     [not found]           ` <1282100145-27485-4-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18  2:55             ` [PATCH 4/5] usb: ohci: omap: Update clock names to be same across OMAP3 and OMAP4 Keshava Munegowda
     [not found]               ` <1282100145-27485-5-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18  2:55                 ` [PATCH 5/6] usb: ohci: don't hard-code TLL channel count Keshava Munegowda
     [not found]                   ` <1282100145-27485-6-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18 15:37                     ` Munegowda, Keshava
2010-08-19  6:03                     ` Felipe Balbi
     [not found]                       ` <20100819060308.GT4385-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2010-08-19  6:26                         ` Munegowda, Keshava
2010-08-19  7:23                           ` Felipe Balbi [this message]
2010-08-19  7:26                             ` Munegowda, Keshava
2010-08-19  6:01           ` [PATCH 3/5] usb: ehci: relocate PHY reset code Felipe Balbi
     [not found]             ` <20100819060126.GS4385-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2010-08-20  9:41               ` Gadiyar, Anand
2010-09-08  7:51 ` [PATCH 0/5] usb: omap: prepare for OMAP4 EHCI and OHCI support Munegowda, Keshava
2010-09-08  8:55   ` Greg KH
2010-09-08  9:49     ` Munegowda, Keshava

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=20100819072312.GV4385@nokia.com \
    --to=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --cc=keshava_mgowda@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox