linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/9] rcar-phy: remove EHCI internal buffer setup
Date: Wed, 10 Apr 2013 18:11:54 +0400	[thread overview]
Message-ID: <5165732A.8050901@cogentembedded.com> (raw)
In-Reply-To: <20130410082748.GJ7983@arwen.pp.htv.fi>

Hello.

On 10-04-2013 12:27, Felipe Balbi wrote:

> On Wed, Apr 10, 2013 at 02:32:30AM +0400, Sergei Shtylyov wrote:
>> Now that the EHCI internal  buffer setup is done by the platform code, we  can
>> remove  such code from this driver as it  never  really belonged here.  We also
>> no longer need the 2nd memory region now (2nd EHCI controller is simply missing
>> in e.g. R8A7778 SoC).

>> The patch has been tested on the Marzen and BOCK-W boards.

>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>> Acked-by: Simon Horman <horms+renesas@verge.net.au>

>> ---
>> Changes since version 2:
>> - added a note about testing to the changelog;
>> - added ACKs from Simon Horman and Kuninori Morimoto.

>> Changes since the original posting:
>> - split R8A7779 SoC file change to a separate patch.

>>   drivers/usb/phy/rcar-phy.c |   28 ++++------------------------

> you do realise this won't apply, right ?

    Because of the rename you've done? No, I didn't realize it until you told.
I wasn't watching changes in your tree...

WBR, Sergei

  reply	other threads:[~2013-04-10 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 22:32 [PATCH v3 4/9] rcar-phy: remove EHCI internal buffer setup Sergei Shtylyov
2013-04-10  8:27 ` Felipe Balbi
2013-04-10 14:11   ` Sergei Shtylyov [this message]
2013-04-10  8:55 ` Felipe Balbi

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=5165732A.8050901@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.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 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).