From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
Date: Tue, 9 Apr 2013 20:32:18 +0200 [thread overview]
Message-ID: <201304092032.18885.arnd@arndb.de> (raw)
In-Reply-To: <5164462E.4010706@codeaurora.org>
On Tuesday 09 April 2013, Stephen Boyd wrote:
> >>>
> >>> Sneaking it in through the fixes branch would make life easier for us,
> >>> but it doesn't feel right.
> >> Arnd, can you pick this up into the arm-soc tree now? It would be good
> >> to get this into next so that conflicts are avoided later on.
> >>
> > Arnd?
> >
>
> Ping?
Sorry for the long delay, you scrolled down from my unread emails twice.
Three tips for you to make it more likely to get a fast reaction time:
* Send the original patch to Olof and me, not just the reply to the
on-list patch.
* Use the arm at kernel.org alias to reach us, since that will make the
email go into the right folder
* Use the [GIT PULL] keyword in the subject line, ideally sending a
pull request as well, instead of a separate email. While we do apply
emails, It's often batch processing to apply everything and then
we scan for emails that have PULL in the subject, while others
can get lost.
I've applied it to the next/soc branch now.
Arnd
next prev parent reply other threads:[~2013-04-09 18:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 23:28 [PATCHv2] ARM: Push selects for TWD/SCU into machine entries Stephen Boyd
2013-02-27 23:43 ` Stephen Warren
2013-03-05 1:45 ` Stephen Boyd
2013-03-05 22:34 ` Arnd Bergmann
2013-03-16 19:32 ` Stephen Boyd
2013-03-26 17:34 ` Stephen Boyd
2013-04-09 16:47 ` Stephen Boyd
2013-04-09 18:32 ` Arnd Bergmann [this message]
2013-04-09 19:35 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2012-10-24 17:24 Stephen Boyd
2012-10-24 17:54 ` Stephen Warren
2012-10-25 18:04 ` Stephen Boyd
2012-10-25 20:34 ` David Brown
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=201304092032.18885.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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