From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3.18] ARM: BCM: Broadcom BCM63138 support
Date: Tue, 16 Sep 2014 18:27:24 +0200 [thread overview]
Message-ID: <201409161827.24548.arnd@arndb.de> (raw)
In-Reply-To: <CAEPRUYrcpaUmLvr4k5GK11wRbQ8XwFQdxRJPeunH7p-w7jL2-Q@mail.gmail.com>
On Monday 15 September 2014, Christian Daudt wrote:
> >
> >
> > Arnd has reviewed v2, and v3 addresses his former comments, he has not
> > replied with an Ack though I do not mind waiting for this.
>
> Ok - explicit is better than implicit. Arnd - can you pls confirm your
> ack to these patches ?
I'm glad you asked, because it triggered me to look at the pull request.
The patches are all good, feel free to add
Acked-by: Arnd Bergmann <arnd@arndb.de>
to each patch, or to the merge, whichever works for you.
However, the pull request was done wrong, so don't merge this changeset
into your branch or we won't pull it from you.
The problem is that it is based on top of out for-next branch, which is
not meant to be sent upstream to Linus. Instead as you know we expect
all pull requests coming in from platform maintainers to be done as
topic branches and normall based on top of the previous -rc1 release,
or possibly a later -rcX release if you have a strong dependency on
a bug fix that went into that release.
I'd recommend that Florian rebases from 244a68e90d0775d3e579 to
v3.17-rc1 and send a new pull request, but it's also fine if you
do the rebase and add your Signed-off-by to the patches in the process.
Arnd
next prev parent reply other threads:[~2014-09-16 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 21:44 [GIT PULL 3.18] ARM: BCM: Broadcom BCM63138 support Florian Fainelli
2014-09-06 14:33 ` Arnd Bergmann
2014-09-06 17:55 ` Florian Fainelli
2014-09-15 4:56 ` Christian Daudt
2014-09-15 5:16 ` Florian Fainelli
2014-09-15 7:14 ` Christian Daudt
2014-09-16 16:27 ` Arnd Bergmann [this message]
2014-09-16 19:09 ` Florian Fainelli
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=201409161827.24548.arnd@arndb.de \
--to=arnd@arndb.de \
--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.