public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Matt Mackall <mpm@selenic.com>,
	Deepak Saxena <dsaxena@plexity.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
	<linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <s-anna@ti.com>,
	Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH] hwrng: OMAP: Fix assumption that runtime_get_sync will always succeed
Date: Fri, 24 Jun 2016 11:54:52 -0500	[thread overview]
Message-ID: <576D65DC.5050205@ti.com> (raw)
In-Reply-To: <1466787040-26184-2-git-send-email-nm@ti.com>

On 06/24/2016 11:50 AM, Nishanth Menon wrote:
> pm_runtime_get_sync does return a error value that must be checked for
> error conditions, else, due to various reasons, the device maynot be
> enabled and the system will crash due to lack of clock to the hardware
> module.
> 


Oh crap! Apologies, please ignore the v1 patch which was unfortunately
reposted. Sorry for the spam - i was pretty sure I cleared out the old
patch, but looks I was wrong.

V2 of the patch is here: https://patchwork.kernel.org/patch/9197919/



-- 
Regards,
Nishanth Menon

  reply	other threads:[~2016-06-24 16:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 16:50 [PATCH V2] hwrng: OMAP: Fix assumption that runtime_get_sync will always succeed Nishanth Menon
2016-06-24 16:50 ` [PATCH] " Nishanth Menon
2016-06-24 16:54   ` Nishanth Menon [this message]
2016-06-27  9:05 ` [PATCH V2] " Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2016-06-24 15:57 [PATCH] " Nishanth Menon
2016-06-24 16:35 ` Suman Anna
2016-06-24 16:46   ` Nishanth Menon

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=576D65DC.5050205@ti.com \
    --to=nm@ti.com \
    --cc=dsaxena@plexity.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=paul@pwsan.com \
    --cc=s-anna@ti.com \
    /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