All of lore.kernel.org
 help / color / mirror / Atom feed
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: berlin: Driver changes for v3.18
Date: Mon, 20 Oct 2014 16:39:12 +0200	[thread overview]
Message-ID: <54451E90.1090403@gmail.com> (raw)
In-Reply-To: <2055721.MLiQlaVx8P@wuerfel>

On 20.10.2014 16:36, Arnd Bergmann wrote:
> On Monday 20 October 2014 16:34:35 Sebastian Hesselbarth wrote:
>> On 01.10.2014 17:03, Arnd Bergmann wrote:
>>> On Tuesday 23 September 2014, Sebastian Hesselbarth wrote:
>>>> Berlin is a little quiet this time. Antoine is still doing a great job
>>>> but ChipIdea USB didn't make it again this time. Let's hope it makes it
>>>> next time.
>>>>
>>>> At least we can add the reset driver contained in this PR.
>>>
>>> I've pulled all three into the next/late branch, we'll decide next week
>>> whether that makes it into 3.18, based on how things go with the stuff
>>> in the normal branches.
>>>
>>> Please try to send stuff earlier next time so it can be part of the
>>> regular submission.
>>
>> Hmm, looks like I was really too late this time. Will try to send
>> earlier PRs next cycle.
>>
>> Anyway, how should I proceed with this now? Do you want me to reapply
>> the patches on v3.18-rc1 and proceed with normal for-v3.19 cycle? Or
>> should I merge arm-soc's next/late into berlin's for-v3.19 branches
>> to apply new patches on top?
>>
>
> The former.
>
> We are not going to use the next/late branch this time, and all code
> in it will be abandoned, so you should send it again.

Ok, so I reapply the patches in question on top of v3.18-rc1.

> Also, you should /never/ base anything on top of any of our next/*
> branches. Always use the minimum set of branches as a base instead.

Ok, just wanted to make sure how you planned to deal with the late
branch.

Sebastian

      reply	other threads:[~2014-10-20 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 22:41 [GIT PULL] ARM: berlin: Driver changes for v3.18 Sebastian Hesselbarth
2014-09-22 22:41 ` [GIT PULL] ARM: berlin: SoC " Sebastian Hesselbarth
2014-09-22 22:41 ` [GIT PULL] ARM: berlin: DT " Sebastian Hesselbarth
2014-10-01 15:03 ` [GIT PULL] ARM: berlin: Driver " Arnd Bergmann
2014-10-20 14:34   ` Sebastian Hesselbarth
2014-10-20 14:36     ` Arnd Bergmann
2014-10-20 14:39       ` Sebastian Hesselbarth [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=54451E90.1090403@gmail.com \
    --to=sebastian.hesselbarth@gmail.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.