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:34:35 +0200 [thread overview]
Message-ID: <54451D7B.20309@gmail.com> (raw)
In-Reply-To: <201410011703.29695.arnd@arndb.de>
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?
Sebastian
next prev parent reply other threads:[~2014-10-20 14:34 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 [this message]
2014-10-20 14:36 ` Arnd Bergmann
2014-10-20 14:39 ` Sebastian Hesselbarth
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=54451D7B.20309@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 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).