From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: Linus' tree (master) not working for Allwinner sun4i, sun5i, sun7i SoC-s + fix
Date: Mon, 15 Dec 2014 17:56:55 +0100 [thread overview]
Message-ID: <20141215165655.GL4337@lukather> (raw)
In-Reply-To: <548F0C8C.3030006@gmail.com>
Hi,
On Mon, Dec 15, 2014 at 05:30:04PM +0100, Hans de Goede wrote:
> Hi Maxime,
>
> Somehow this commit of your sunxi/clocks-for-3.19 branch has made it
> into Linus' tree:
>
> https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/commit/?h=sunxi/clocks-for-3.19&id=93746e70be83a3f113134a16065957b324af50f7
>
> But this one has not:
>
> https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/commit/?h=sunxi/clocks-for-3.19&id=acbcc0f03b15585387f9ca69c2a976b02cb69023
>
> Rather badly breaking Allwinner sun4i, sun5i, sun7i SoC-s.
I don't know what you are looking at, but I don't see any of these
commits in Linus' current master, either in the git repo itself, or
using the kernel.org git interface.
They're both part of Mike Turquette's clk-next though, so they should
both land just fine whenever that will be merged.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141215/afac3ffd/attachment.sig>
next prev parent reply other threads:[~2014-12-15 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 16:30 Linus' tree (master) not working for Allwinner sun4i, sun5i, sun7i SoC-s + fix Hans de Goede
2014-12-15 16:56 ` Maxime Ripard [this message]
2014-12-15 17:06 ` [linux-sunxi] " Hans de Goede
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=20141215165655.GL4337@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).