From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] ARM: mvebu: soc changes for v3.11 (round 2 cumulative)
Date: Mon, 3 Jun 2013 10:46:38 -0400 [thread overview]
Message-ID: <20130603144638.GI3803@titan.lakedaemon.net> (raw)
In-Reply-To: <20130601053835.GI5189@quad.lixom.net>
On Fri, May 31, 2013 at 10:38:35PM -0700, Olof Johansson wrote:
> On Wed, May 29, 2013 at 03:36:54PM -0400, Jason Cooper wrote:
> > Olof,
> >
> > Since I have a few hours, I added a Tested-by that I thought I
> > missed. No other changes.
>
> All these respins are making it hard to track your pull requests, by
> the way. Some of them are threaded, other are not. And the numbering
> doesn't align, some are round 2, others are around 3.
>
> Can you thread all of them, per chance? That way it's easy to tell which ones
> belonged in the old group and can just be discarded.
Sure, I was trying to only thread them if there were dependencies
between the branches (of_pci, pcie, pcie_bridge, etc), but will do so in
the future.
thx,
Jason.
next prev parent reply other threads:[~2013-06-03 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 18:36 [GIT PULL] ARM: mvebu: soc changes for v3.11 (round 2 cumulative) Jason Cooper
2013-05-29 19:36 ` [GIT PULL v2] " Jason Cooper
2013-06-01 5:38 ` Olof Johansson
2013-06-03 14:46 ` Jason Cooper [this message]
2013-06-01 5:41 ` Olof Johansson
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=20130603144638.GI3803@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