From: sboyd@codeaurora.org (Stephen Boyd)
To: linus-amlogic@lists.infradead.org
Subject: [GIT PULL] Amlogic clock driver updates for 4.13
Date: Fri, 2 Jun 2017 10:58:48 -0700 [thread overview]
Message-ID: <20170602175848.GM20170@codeaurora.org> (raw)
In-Reply-To: <1496416942.3552.8.camel@baylibre.com>
On 06/02, Jerome Brunet wrote:
> Dear clock maintainers,
>
> Below is a request to pull the Amlogic clock driver updates for this cycle.
>
> Cheers
Thanks. Pulled into clk-next.
--
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: Stephen Boyd <sboyd@codeaurora.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Neil Armstrong <narmstrong@baylibre.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>
Subject: Re: [GIT PULL] Amlogic clock driver updates for 4.13
Date: Fri, 2 Jun 2017 10:58:48 -0700 [thread overview]
Message-ID: <20170602175848.GM20170@codeaurora.org> (raw)
In-Reply-To: <1496416942.3552.8.camel@baylibre.com>
On 06/02, Jerome Brunet wrote:
> Dear clock maintainers,
>
> Below is a request to pull the Amlogic clock driver updates for this cycle.
>
> Cheers
Thanks. Pulled into clk-next.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-02 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 15:22 [GIT PULL] Amlogic clock driver updates for 4.13 Jerome Brunet
2017-06-02 15:22 ` Jerome Brunet
2017-06-02 17:58 ` Stephen Boyd [this message]
2017-06-02 17:58 ` 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=20170602175848.GM20170@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linus-amlogic@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 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.