From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3] ARM: shmobile: Mark all SoCs in shmobile as CPUFreq, capable
Date: Fri, 20 Jun 2014 01:18:01 +0000 [thread overview]
Message-ID: <20140620011801.GC27743@verge.net.au> (raw)
In-Reply-To: <538FE8D8.3050602@bp.renesas.com>
On Thu, Jun 19, 2014 at 06:16:13PM +0900, Gaku Inami wrote:
> Hi Simon-san,
>
> (2014/06/19 17:09), Simon Horman wrote:
> >
> > Inami-san, could you please make an appropriate patch?
> >
> > Please note the dependency on the patch that Paul has noted,
> > hopefully it will be included in v3.16-rc2.
>
> I understand. I will fix it and send again.
Please just send an (probably small) incremental patch that applies
on top of my current devel branch. There is no need to rework
your patches that I have already queued up.
Thanks
next prev parent reply other threads:[~2014-06-20 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 3:49 [PATCH v3] ARM: shmobile: Mark all SoCs in shmobile as CPUFreq, capable Gaku Inami
2014-06-05 4:09 ` Simon Horman
2014-06-19 7:49 ` Paul Bolle
2014-06-19 8:09 ` Simon Horman
2014-06-19 9:16 ` Gaku Inami
2014-06-20 1:18 ` Simon Horman [this message]
2014-06-20 4:40 ` Gaku Inami
2014-06-20 5:04 ` Simon Horman
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=20140620011801.GC27743@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).