From: Stephen Boyd <sboyd@codeaurora.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH] clk: scpi: error when clock fails to register
Date: Wed, 28 Jun 2017 15:33:34 -0700 [thread overview]
Message-ID: <20170628223334.GD5316@codeaurora.org> (raw)
In-Reply-To: <3e77fd3c-9807-10d4-3a8c-cab8b5562f6c@arm.com>
On 06/28, Sudeep Holla wrote:
> everything if some piece of firmware is not yet ready or broken.
> But again, we can get it working later, for now, I am fine with you patch.
>
So that's an acked-by, reviewed-by tag for the original patch?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: scpi: error when clock fails to register
Date: Wed, 28 Jun 2017 15:33:34 -0700 [thread overview]
Message-ID: <20170628223334.GD5316@codeaurora.org> (raw)
In-Reply-To: <3e77fd3c-9807-10d4-3a8c-cab8b5562f6c@arm.com>
On 06/28, Sudeep Holla wrote:
> everything if some piece of firmware is not yet ready or broken.
> But again, we can get it working later, for now, I am fine with you patch.
>
So that's an acked-by, reviewed-by tag for the original patch?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-28 22:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 13:53 [PATCH] clk: scpi: error when clock fails to register Jerome Brunet
2017-06-28 13:53 ` Jerome Brunet
2017-06-28 15:04 ` Sudeep Holla
2017-06-28 15:04 ` Sudeep Holla
2017-06-28 15:38 ` Jerome Brunet
2017-06-28 15:38 ` Jerome Brunet
2017-06-28 15:52 ` Sudeep Holla
2017-06-28 15:52 ` Sudeep Holla
2017-06-28 16:46 ` Jerome Brunet
2017-06-28 16:46 ` Jerome Brunet
2017-06-28 17:07 ` Sudeep Holla
2017-06-28 17:07 ` Sudeep Holla
2017-06-28 22:33 ` Stephen Boyd [this message]
2017-06-28 22:33 ` Stephen Boyd
2017-06-29 8:50 ` Jerome Brunet
2017-06-29 8:50 ` Jerome Brunet
2017-06-29 9:12 ` Sudeep Holla
2017-06-29 9:12 ` Sudeep Holla
2017-06-29 9:03 ` Sudeep Holla
2017-06-29 9:03 ` Sudeep Holla
2017-06-30 0:25 ` Stephen Boyd
2017-06-30 0:25 ` Stephen Boyd
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=20170628223334.GD5316@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=sudeep.holla@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.