linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] cpufreq: i.MX6: -EPROBE_DEFER fixes
Date: Fri, 11 Dec 2015 18:23:11 +0100	[thread overview]
Message-ID: <1449854591.29174.2.camel@pengutronix.de> (raw)
In-Reply-To: <1446019154-16384-1-git-send-email-s.hauer@pengutronix.de>

Am Mittwoch, den 28.10.2015, 08:59 +0100 schrieb Sascha Hauer:
> The i.MX6 cpufreq driver can't cope with -EPROBE_DEFER returned from
> regulator_get/clk_get. This series fix that and some other small
> issues.
> 
> Shawn, Could you give me your ack for patch 4/5?
> 
> Sascha
> 
What's the status of this series? I think I only had some minor
comments on the last round. Can you please fix those and resend the
series? It would be a shame if this misses 4.5, as it includes some
really nice cleanups and fixes.

Regards,
Lucas

> Changes since v1:
> 
> - Fix Coding style nitpicks
> - drop unnecessary platform_device argument from
> ? imx6q_cpufreq_get_resources
> - Add more comments
> - Use id_table to distinguish between SoCs
> - make PU regulator non optional on SoCs that need it and don't
> request
> ? it on SoCs that don't need it
> 
> ----------------------------------------------------------------
> Sascha Hauer (5):
> ??????cpufreq: imx6q: Fix goto wrong error label
> ??????cpufreq: imx6q: Fix wrong device in devm_kzalloc
> ??????cpufreq: imx6q: Fix regulator/clock error handling
> ??????cpufreq: imx6q: Use id_table to distinguish between SoCs
> ??????cpufreq: imx6q: pu regulator is not optional
> 
> ?arch/arm/mach-imx/mach-imx6sl.c |???2 +-
> ?arch/arm/mach-imx/mach-imx6sx.c |???2 +-
> ?arch/arm/mach-imx/mach-imx6ul.c |???2 +-
> ?drivers/cpufreq/imx6q-cpufreq.c | 213 ++++++++++++++++++++++++++--
> ------------
> ?4 files changed, 145 insertions(+), 74 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm"
> in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at??http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2015-12-11 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  7:59 [PATCH v2] cpufreq: i.MX6: -EPROBE_DEFER fixes Sascha Hauer
2015-10-28  7:59 ` [PATCH 1/5] cpufreq: imx6q: Fix goto wrong error label Sascha Hauer
2015-10-28  7:59 ` [PATCH 2/5] cpufreq: imx6q: Fix wrong device in devm_kzalloc Sascha Hauer
2015-10-28  8:49   ` Lucas Stach
2015-10-28  7:59 ` [PATCH 3/5] cpufreq: imx6q: Fix regulator/clock error handling Sascha Hauer
2015-10-28  8:51   ` Lucas Stach
2015-10-28  7:59 ` [PATCH 4/5] cpufreq: imx6q: Use id_table to distinguish between SoCs Sascha Hauer
2015-10-28  9:00   ` Lucas Stach
2015-12-14  1:30   ` Shawn Guo
2015-10-28  7:59 ` [PATCH 5/5] cpufreq: imx6q: pu regulator is not optional Sascha Hauer
2015-12-11 17:23 ` Lucas Stach [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=1449854591.29174.2.camel@pengutronix.de \
    --to=l.stach@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).