From: Stephen Boyd <sboyd@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Turquette <mturquette@baylibre.com>,
Saravana Kannan <saravanak@google.com>
Cc: Saravana Kannan <saravanak@google.com>,
kernel-team@android.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Add sync_state() support to clock framework
Date: Wed, 07 Apr 2021 17:29:19 -0700 [thread overview]
Message-ID: <161784175956.3790633.6032492675008535412@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210407034456.516204-1-saravanak@google.com>
Quoting Saravana Kannan (2021-04-06 20:44:53)
> Stephen,
>
> We can decide later if both these patches land through clk tree or the
> driver-core tree. The meat of the series is in Patch 2/2 and that commit
> text gives all the details.
The majority of the diff is in drivers/clk so presumably it can be
merged through the clk tree if Greg acks the include file API.
>
> Saravana Kannan (2):
> driver core: Add dev_set_drv_sync_state()
> clk: Add support for sync_state()
>
> drivers/clk/clk.c | 84 +++++++++++++++++++++++++++++++++++-
> include/linux/clk-provider.h | 1 +
> include/linux/device.h | 12 ++++++
> 3 files changed, 96 insertions(+), 1 deletion(-)
next prev parent reply other threads:[~2021-04-08 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 3:44 [PATCH v1 0/2] Add sync_state() support to clock framework Saravana Kannan
2021-04-07 3:44 ` [PATCH v1 1/2] driver core: Add dev_set_drv_sync_state() Saravana Kannan
2021-04-08 6:41 ` Greg Kroah-Hartman
2021-04-07 3:44 ` [PATCH v1 2/2] clk: Add support for sync_state() Saravana Kannan
2021-04-14 17:45 ` Saravana Kannan
2021-06-25 22:37 ` Stephen Boyd
2023-05-09 7:16 ` Abel Vesa
2021-04-08 0:29 ` Stephen Boyd [this message]
2021-04-08 6:41 ` [PATCH v1 0/2] Add sync_state() support to clock framework Greg Kroah-Hartman
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=161784175956.3790633.6032492675008535412@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=saravanak@google.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.