From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Mike Turquette <mturquette@baylibre.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: [GIT PULL] clk/samsung updates for v4.11, part 2
Date: Mon, 30 Jan 2017 18:05:32 +0100 [thread overview]
Message-ID: <380eea9f-401b-f83f-4420-f89810086278@samsung.com> (raw)
In-Reply-To: <20170127195537.GG8801@codeaurora.org>
On 01/27/2017 08:55 PM, Stephen Boyd wrote:
> On 01/27, Sylwester Nawrocki wrote:
>> Hi Stephen, Mike,
>>
>> The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:
>>
>> Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)
>>
>> are available in the git repository at:
>>
>> git://linuxtv.org/snawrocki/samsung.git tags/clk-v4.11-samsung-2
>>
>> for you to fetch changes up to 02c952c8f95fd0adf1835704db95215f57cfc8e6:
>>
>> clk: samsung: mark s3c...._clk_sleep_init() as __init (2017-01-27 13:30:00 +0100)
>>
>> ----------------------------------------------------------------
>> Exporting clock IDs for Exynos5433 SoC MIPI DSI DPHY,
>> Exynos PLL code updates and overall minor clean-ups.
>>
> Thanks. Pulled into clk-next.
>
> Can you get your key signed by more people? Maybe others at
> Samsung?
That has been on my todo list for quite long time, thanks for
reminding. My key got signed already by one more person and
there should be two more before I'm sending next pull request.
--
Regards,
Sylwester
prev parent reply other threads:[~2017-01-30 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170127172254epcas1p41085b7154dba751e0c19d4f92a8558a7@epcas1p4.samsung.com>
2017-01-27 17:22 ` [GIT PULL] clk/samsung updates for v4.11, part 2 Sylwester Nawrocki
2017-01-27 19:55 ` Stephen Boyd
2017-01-30 17:05 ` Sylwester Nawrocki [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=380eea9f-401b-f83f-4420-f89810086278@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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.