From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/8] rcar-phy: remove EHCI internal buffer setup
Date: Fri, 05 Apr 2013 20:28:19 +0400 [thread overview]
Message-ID: <515EFBA3.7040702@cogentembedded.com> (raw)
In-Reply-To: <20130405004300.GO29203@verge.net.au>
Hello.
On 05-04-2013 4:43, Simon Horman 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).
> I wonder if this patch could be split into a driver patch
> followed by an SoC patch. Or vice versa.
This one indeed can, I just tried to somewhat save on patches. But not
vice versa, of course, that'll break bisection. :-)
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
WBR, Sergei
prev parent reply other threads:[~2013-04-05 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 23:03 [PATCH 4/8] rcar-phy: remove EHCI internal buffer setup Sergei Shtylyov
2013-04-05 0:43 ` Simon Horman
2013-04-05 16:28 ` Sergei Shtylyov [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=515EFBA3.7040702@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).