linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Ansuel Smith <ansuelsmth@gmail.com>, agross@kernel.org
Cc: Ansuel Smith <ansuelsmth@gmail.com>,
	Abhishek Sahu <absahu@codeaurora.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Kumar Gala <galak@codeaurora.org>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] ipq806x: gcc: Added the enable regs and mask for PRNG
Date: Mon, 16 Mar 2020 11:31:21 -0700	[thread overview]
Message-ID: <158438348176.88485.14753820783752413756@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200314133600.183-1-ansuelsmth@gmail.com>

Quoting Ansuel Smith (2020-03-14 06:36:00)
> Kernel got hanged while reading from /dev/hwrng at the
> time of PRNG clock enable

Authorship is still wrong. There should be a From: Abhishek Sahu
<absahu@codeaurora.org> line above this line.

> 
> Fixes: 24d8fba44af3 "clk: qcom: Add support for IPQ8064's global
> clock controller (GCC)"
> 
> Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
> Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
> ---

Also, please don't send as a reply to the older versions of this patch.
It makes it harder to keep track of what is new and what isn't new and
buries it deep in a thread for me.

      reply	other threads:[~2020-03-16 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 18:54 [PATCH] ipq806x: gcc: Added the enable regs and mask for PRNG Ansuel Smith
2020-03-13 20:30 ` Stephen Boyd
2020-03-13 21:20   ` R: " ansuelsmth
2020-03-14  1:15     ` Stephen Boyd
2020-03-14 13:36   ` [RESEND PATCH] " Ansuel Smith
2020-03-16 18:31     ` Stephen Boyd [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=158438348176.88485.14753820783752413756@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=absahu@codeaurora.org \
    --cc=agross@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=galak@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.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;
as well as URLs for NNTP newsgroup(s).