From: Olof Johansson <olof@lixom.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "arm@kernel.org" <arm@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
cpufreq@vger.kernel.org
Subject: Re: [GIT PULL] Integrator DTS and defconfig changes
Date: Fri, 18 Nov 2016 09:53:01 -0800 [thread overview]
Message-ID: <20161118175301.GA8882@localhost> (raw)
In-Reply-To: <CACRpkdYoornJx1fTN1C5OiR16w9DbTcr9ze4gc9PLkt7LCqqCQ@mail.gmail.com>
On Fri, Nov 18, 2016 at 09:26:56AM +0100, Linus Walleij wrote:
> On Fri, Nov 18, 2016 at 8:25 AM, Olof Johansson <olof@lixom.net> wrote:
>
> > I also sympathize that it's extra annoying having to split just three
> > patches across two branches. So, if it's easier we can just cherry-pick
> > apart the patches here across the branches (your comment about next
> > coverage makes me suspect you have no direct downstream users of this
> > branch). If that's OK, let me know and I'll do that tomorrow.
>
> It's fine to cherry-pick, I can also send two separate branches (or
> just 2+1 stand-alone patches).
>
> Any way you like it :) just tell me what to do, all I want is to get this
> in for v4.10.
Cherry-picking is actually faster on our side than merging, so I've done that
now. Queued into next/dt and next/defconfig for 4.10.
Thanks!
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Integrator DTS and defconfig changes
Date: Fri, 18 Nov 2016 09:53:01 -0800 [thread overview]
Message-ID: <20161118175301.GA8882@localhost> (raw)
In-Reply-To: <CACRpkdYoornJx1fTN1C5OiR16w9DbTcr9ze4gc9PLkt7LCqqCQ@mail.gmail.com>
On Fri, Nov 18, 2016 at 09:26:56AM +0100, Linus Walleij wrote:
> On Fri, Nov 18, 2016 at 8:25 AM, Olof Johansson <olof@lixom.net> wrote:
>
> > I also sympathize that it's extra annoying having to split just three
> > patches across two branches. So, if it's easier we can just cherry-pick
> > apart the patches here across the branches (your comment about next
> > coverage makes me suspect you have no direct downstream users of this
> > branch). If that's OK, let me know and I'll do that tomorrow.
>
> It's fine to cherry-pick, I can also send two separate branches (or
> just 2+1 stand-alone patches).
>
> Any way you like it :) just tell me what to do, all I want is to get this
> in for v4.10.
Cherry-picking is actually faster on our side than merging, so I've done that
now. Queued into next/dt and next/defconfig for 4.10.
Thanks!
-Olof
next prev parent reply other threads:[~2016-11-18 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 8:10 [GIT PULL] Integrator DTS and defconfig changes Linus Walleij
2016-11-09 8:10 ` Linus Walleij
2016-11-18 7:25 ` Olof Johansson
2016-11-18 7:25 ` Olof Johansson
2016-11-18 8:26 ` Linus Walleij
2016-11-18 8:26 ` Linus Walleij
2016-11-18 17:53 ` Olof Johansson [this message]
2016-11-18 17:53 ` Olof Johansson
2016-11-19 15:19 ` Linus Walleij
2016-11-19 15:19 ` Linus Walleij
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=20161118175301.GA8882@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=cpufreq@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--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.