From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/4] ARM: mvebu: changes for v3.9
Date: Mon, 4 Feb 2013 07:05:14 -0500 [thread overview]
Message-ID: <20130204120514.GK14746@titan.lakedaemon.net> (raw)
In-Reply-To: <510F7156.70005@free-electrons.com>
On Mon, Feb 04, 2013 at 09:29:10AM +0100, Gregory CLEMENT wrote:
> Hi Jason,
>
> On 02/01/2013 04:51 PM, Jason Cooper wrote:
> > The following changes since commit 19d23dac1b8f95e4a960fcbbb5687c33b9a2cd01:
> >
> > Merge branch 'fixes' into for-next
> >
> > are available in the git repository at:
> >
> > git://git.infradead.org/users/jcooper/linux.git mvebu/for-next
> >
> > for you to fetch changes up to 7d8a7dce24f76242daf1c469878597b8acc4f78f:
> >
> > Merge tag 'tags/dt_for_v3.9' into mvebu/for-next
> >
> > Jason Cooper (5):
> > Merge tag 'tags/mvebu_fixes_for_v3.8-rc6' into mvebu/for-next
> > Merge tag 'tags/cleanup_for_v3.9_round2' into mvebu/for-next
> > Merge tag 'tags/drivers_for_v3.9' into mvebu/for-next
> > Merge tag 'tags/boards_for_v3.9' into mvebu/for-next
> > Merge tag 'tags/dt_for_v3.9' into mvebu/for-next
>
> I didn't see anything about the USB support for Armada370/XP sent
> by Ezequiel. Is there any reason to not have it? Or do you plan
> to send a new pull request soon with his patch set?
Yes, this is a redo of the first series of requests I sent out. I had
to move mvsdio out to the appropriate maintainer tree and depend on it.
As soon as this gets pulled in, I have another round with everything but
Thomas' pci work. His will most likely be a separate pr series.
> PS: I noticed that there are a some files not related to mvebu at all
> (such as the arch/parisc/... for example), but I guess it is due to some
> dependencies.
Yeah, I'm working on that. It's purely in the diffstat, so it's not a
show stopper. It's much cleaner than the first time around, which is an
improvement.
thx,
Jason.
next prev parent reply other threads:[~2013-02-04 12:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 15:51 [GIT PULL 0/4] ARM: mvebu: changes for v3.9 Jason Cooper
2013-02-01 15:51 ` [GIT PULL 1/4] ARM: mvebu: cleanup " Jason Cooper
2013-02-05 7:10 ` Olof Johansson
2013-02-01 15:51 ` [GIT PULL 3/4] ARM: mvebu: boards " Jason Cooper
2013-02-05 7:10 ` Olof Johansson
2013-02-05 11:21 ` Jason Cooper
2013-02-05 18:23 ` Olof Johansson
2013-02-05 18:30 ` Jason Cooper
2013-02-05 23:26 ` Olof Johansson
2013-02-06 13:20 ` Jason Cooper
2013-02-10 0:31 ` Olof Johansson
2013-02-10 21:05 ` Jason Cooper
2013-02-01 15:51 ` [GIT PULL 2/4] ARM: mvebu: drivers " Jason Cooper
2013-02-05 7:10 ` Olof Johansson
2013-02-01 15:51 ` [GIT PULL 4/4] ARM: mvebu: dt " Jason Cooper
2013-02-04 8:29 ` [GIT PULL 0/4] ARM: mvebu: changes " Gregory CLEMENT
2013-02-04 12:05 ` Jason Cooper [this message]
[not found] <510be4a4.4cf8dc0a.6acf.ffffcbc6SMTPIN_ADDED_BROKEN@mx.google.com>
2013-02-05 6:29 ` Olof Johansson
2013-02-05 12:18 ` Jason Cooper
-- strict thread matches above, loose matches on Subject: below --
2013-01-12 23:29 Jason Cooper
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=20130204120514.GK14746@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