All of lore.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Wrong location of omap_writel?
Date: Mon, 28 May 2012 04:04:51 -0700	[thread overview]
Message-ID: <20120528110451.GB12766@atomide.com> (raw)
In-Reply-To: <3426836.dn1rYLBNLa@dizzy-6>

* David Lanzend?rfer <david.lanzendoerfer@o2s.ch> [120528 02:07]:
> Hi
> 
> Under linux-next 20120528
> 
> I've just found "omap_writel" within "arch/arm/plat-omap/include/plat/usb.h"...
> Shouldn't it be located within "arch/arm/plat-omap/include/plat/io.h"?
> 
> Just some logical question.
> It looks somehow wrong to me...

It's in usb.h as the legacy full speed usb code is the only remaining user
for omap_read/write for omap2+.

I've also posted a series that removes the legacy full speed usb code and
omap_read/write for omap2+ for v3.6 merge window.

Regards,

Tony

      reply	other threads:[~2012-05-28 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28  9:00 Wrong location of omap_writel? David Lanzendörfer
2012-05-28 11:04 ` Tony Lindgren [this message]

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=20120528110451.GB12766@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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.