From: Stephen Boyd <sboyd@codeaurora.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Mike Turquette <mturquette@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
Chen-Yu Tsai <wens@csie.org>,
linux-clk@vger.kernel.org
Subject: Re: [GIT PULL] Allwinner clock fixes for 4.12
Date: Wed, 14 Jun 2017 16:50:42 -0700 [thread overview]
Message-ID: <20170614235042.GF20170@codeaurora.org> (raw)
In-Reply-To: <20170614192119.xktlt4o5puje2pdu@flea.home>
On 06/14, Maxime Ripard wrote:
> Hi Mike, Stephen,
>
> Please pull the following patches for 4.12
>
> Thanks!
> Maxime
>
> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>
> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git tags/sunxi-clk-fixes-for-4.12
>
> for you to fetch changes up to d85da227c3ae43d9ca513d60f244213cb4e55485:
>
> clk: sunxi-ng: a64: Export PLL_PERIPH0 clock for the PRCM (2017-05-31 21:57:30 +0200)
>
> ----------------------------------------------------------------
> Allwinner clock fixes for 4.12
>
> Some fixes that fix some bindings that went in 4.12, fix a few reset and
> clock offsets and a build error fix
>
The last few don't have any Fixes: tag. Is that because they
aren't fixes for anything in the tree? I pulled it, but I'm
second guessing it all.
--
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: [GIT PULL] Allwinner clock fixes for 4.12
Date: Wed, 14 Jun 2017 16:50:42 -0700 [thread overview]
Message-ID: <20170614235042.GF20170@codeaurora.org> (raw)
In-Reply-To: <20170614192119.xktlt4o5puje2pdu@flea.home>
On 06/14, Maxime Ripard wrote:
> Hi Mike, Stephen,
>
> Please pull the following patches for 4.12
>
> Thanks!
> Maxime
>
> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>
> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git tags/sunxi-clk-fixes-for-4.12
>
> for you to fetch changes up to d85da227c3ae43d9ca513d60f244213cb4e55485:
>
> clk: sunxi-ng: a64: Export PLL_PERIPH0 clock for the PRCM (2017-05-31 21:57:30 +0200)
>
> ----------------------------------------------------------------
> Allwinner clock fixes for 4.12
>
> Some fixes that fix some bindings that went in 4.12, fix a few reset and
> clock offsets and a build error fix
>
The last few don't have any Fixes: tag. Is that because they
aren't fixes for anything in the tree? I pulled it, but I'm
second guessing it all.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-14 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 19:21 [GIT PULL] Allwinner clock fixes for 4.12 Maxime Ripard
2017-06-14 19:21 ` Maxime Ripard
2017-06-14 23:50 ` Stephen Boyd [this message]
2017-06-14 23:50 ` Stephen Boyd
2017-06-20 7:45 ` Maxime Ripard
2017-06-20 7:45 ` Maxime Ripard
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=20170614235042.GF20170@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=wens@csie.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.