All of lore.kernel.org
 help / color / mirror / Atom feed
From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: Linus' tree (master) not working for Allwinner sun4i, sun5i, sun7i SoC-s + fix
Date: Mon, 15 Dec 2014 18:06:28 +0100	[thread overview]
Message-ID: <548F1514.8090404@redhat.com> (raw)
In-Reply-To: <20141215165655.GL4337@lukather>

Hi,

On 15-12-14 17:56, Maxime Ripard wrote:
> 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.

Ah you're right, I had all patches from your sunxi/clocks-for-3.19 in my
local tree, and when rebasing on Linus' latest somehow the second one
got dropped on the rebase ?

I did not do any manual work on the rebase it went straight ahead, so
I don't understand how the patch got dropped. Anyways as you said
neither one is in Linus' tree atm, so this is not a problem, sorry
for the noise.

Regards,

Hans

WARNING: multiple messages have this Message-ID (diff)
From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	Hans de Goede
	<j.w.r.degoede-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-arm-kernel
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Subject: Re: Re: Linus' tree (master) not working for Allwinner sun4i, sun5i, sun7i SoC-s + fix
Date: Mon, 15 Dec 2014 18:06:28 +0100	[thread overview]
Message-ID: <548F1514.8090404@redhat.com> (raw)
In-Reply-To: <20141215165655.GL4337@lukather>

Hi,

On 15-12-14 17:56, Maxime Ripard wrote:
> 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.

Ah you're right, I had all patches from your sunxi/clocks-for-3.19 in my
local tree, and when rebasing on Linus' latest somehow the second one
got dropped on the rebase ?

I did not do any manual work on the rebase it went straight ahead, so
I don't understand how the patch got dropped. Anyways as you said
neither one is in Linus' tree atm, so this is not a problem, sorry
for the noise.

Regards,

Hans

  reply	other threads:[~2014-12-15 17:06 UTC|newest]

Thread overview: 6+ 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:30 ` Hans de Goede
2014-12-15 16:56 ` Maxime Ripard
2014-12-15 16:56   ` Maxime Ripard
2014-12-15 17:06   ` Hans de Goede [this message]
2014-12-15 17:06     ` 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=548F1514.8090404@redhat.com \
    --to=hdegoede@redhat.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 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.