linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gaku Inami <gaku.inami.xw@bp.renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 7/8] ARM: shmobile: Make r8a7791 CPUFreq capable
Date: Thu, 05 Jun 2014 01:04:45 +0000	[thread overview]
Message-ID: <538FC22D.9000604@bp.renesas.com> (raw)
In-Reply-To: <538DB98D.20009@bp.renesas.com>

Hi Magnus-san,

Thank you for your feedback.
 

> Thanks for your patches. In general they look good, but I wonder about
> this Kconfig magic for r8a7790 and r8a7791.
>
> Instead of enabling the above for r8a7790 and r8a7791, how about
> enabling it for all SoCs included in ARCH_SHMOBILE_MULTI?

I will add this fix into ARCH_SHMOBILE_MULTI for all SoCs, and resend it.

Regards,
Inami


      parent reply	other threads:[~2014-06-05  1:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 12:03 [PATCH v2 7/8] ARM: shmobile: Make r8a7791 CPUFreq capable Gaku Inami
2014-06-04 12:08 ` Magnus Damm
2014-06-05  1:04 ` Gaku Inami [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=538FC22D.9000604@bp.renesas.com \
    --to=gaku.inami.xw@bp.renesas.com \
    --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).