From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Improve the SMP support of the interrupt controller for Armada XP
Date: Wed, 5 Dec 2012 15:58:48 -0500 [thread overview]
Message-ID: <20121205205848.GX12509@titan.lakedaemon.net> (raw)
In-Reply-To: <50BFB23C.5040906@free-electrons.com>
On Wed, Dec 05, 2012 at 09:44:44PM +0100, Gregory CLEMENT wrote:
> On 12/05/2012 09:36 PM, Jason Cooper wrote:
> > On Wed, Dec 05, 2012 at 09:28:59PM +0100, Gregory CLEMENT wrote:
> >> On 12/05/2012 02:33 PM, Gregory CLEMENT wrote:
> >>> Jason,
> >>>
> >>> here it is the patch set to improve the Armada XP SMP support. This
> >>> pull can be merged without any conflict even on the last
> >>> arm-soc/for-next. As Linus Torvalds told that the release of 3.7 won't
> >>> happen before next week, I'd like to have this improvement as part of
> >>> 3.8.
> >>>
> >>
> >> Please ignore this git pull, the code is buggy in non-SMP mode. A new
> >> version is incoming. Sorry.
> >
> > Ok, please do me a favor and don't send pull requests until patches have
> > had sufficient review on lakml.
> >
>
> OK, I will
Just to be clear, I don't mind if you throw it up on your public repo
and put the git pull info in a cover letter or the remarks section of
patch email. The problem is when folks see 'GIT PULL' in the subject,
they assume it has already been reviewed. And, thus, don't review it.
hth,
Jason.
prev parent reply other threads:[~2012-12-05 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 13:33 [GIT PULL] Improve the SMP support of the interrupt controller for Armada XP Gregory CLEMENT
2012-12-05 13:33 ` [PATCH] arm: mvebu: Improve the SMP support of the interrupt controller Gregory CLEMENT
2012-12-05 20:28 ` [GIT PULL] Improve the SMP support of the interrupt controller for Armada XP Gregory CLEMENT
2012-12-05 20:36 ` Jason Cooper
2012-12-05 20:44 ` Gregory CLEMENT
2012-12-05 20:58 ` Jason Cooper [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=20121205205848.GX12509@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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