linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] USB mxs-phy: use readl(), writel() instead of the _relaxed() versions
Date: Fri, 08 Mar 2013 17:31:41 +0100	[thread overview]
Message-ID: <513A126D.5080906@pengutronix.de> (raw)
In-Reply-To: <20130308162807.GD32368@arwen.pp.htv.fi>

On 03/08/2013 05:28 PM, Felipe Balbi wrote:
> Hi,
> 
> On Fri, Mar 08, 2013 at 05:05:58PM +0100, Marc Kleine-Budde wrote:
>> On 02/28/2013 12:25 PM, Alexander Shishkin wrote:
>>> Marc Kleine-Budde <mkl@pengutronix.de> writes:
>>>
>>>> This patch converts the mxs-phy driver from readl_relaxed(), writel_relaxed()
>>>> to the plain readl(), writel() functions, which are available on all platforms.
>>>> This is done to enable compile time testing on non ARM platforms.
>>>>
>>>> Reported-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
>>>
>>> I think it was Felipe who reported this actually.
>>
>> Fixed. I'm about to repost this series with crediting Felipe as reporter.
>>
>> Which tree would you like to be this series based on? It depends on the
>> "USB otg: use try_module_get in all usb_get_phy functions and add
>> missing module_put" patch which is part of your usb/fixes branch, but
>> not in usb/next yet.
> 
> look at my testing branch. I have them all already. You didn't get an
> email yet because I'm waiting for -rc2 to be tagged.

Thanks.

> I have fixed the Reported-by tag, no issues there.
> 
> Anyway, as soon as v3.9-rc2 is tagged, I will rebase testing on top of
> that and move all patches to 'next', then everything will be stable from
> that point on.
> 
> If you want to have changes to any of the patches, now is the time,
> after I move patches to 'next' the tree becomes immutable.

Nope, I just wanted to keep track of the patches.

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130308/f1700416/attachment.sig>

  reply	other threads:[~2013-03-08 16:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 10:52 [PATCH 0/4] otg-for-v3.10-v2: separate phy code and add DT helper Marc Kleine-Budde
2013-02-28 10:52 ` [PATCH 1/4] USB: move bulk of otg/otg.c to phy/phy.c Marc Kleine-Budde
2013-02-28 10:52 ` [PATCH 2/4] USB: add devicetree helpers for determining dr_mode and phy_type Marc Kleine-Budde
2013-02-28 10:52 ` [PATCH 3/4] USB mxs-phy: use readl(), writel() instead of the _relaxed() versions Marc Kleine-Budde
2013-02-28 11:25   ` Alexander Shishkin
2013-03-08 16:05     ` Marc Kleine-Budde
2013-03-08 16:28       ` Felipe Balbi
2013-03-08 16:31         ` Marc Kleine-Budde [this message]
2013-03-08 16:34           ` Felipe Balbi
2013-02-28 10:52 ` [PATCH 4/4] USB mxs-phy: Register phy with framework Marc Kleine-Budde

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=513A126D.5080906@pengutronix.de \
    --to=mkl@pengutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).