From: "H. Peter Anvin" <hpa@zytor.com>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
linux-kernel@vger.kernel.org,
Davide Ciminaghi <ciminaghi@gnudd.com>
Subject: Re: tip/x86/amba
Date: Wed, 20 Feb 2013 10:08:01 -0800 [thread overview]
Message-ID: <51251101.5070008@zytor.com> (raw)
In-Reply-To: <20130220073554.GA10939@mail.gnudd.com>
On 02/19/2013 11:35 PM, Alessandro Rubini wrote:
> Hello Peter and maintainers.
>
> I wonder what are the plans for the branch x86/amba, part of the tip
> repository. Of the 7 patches in that branch, 2 are already upstream
> and the other 5 rebase perfectly (only conflicts are in the header
> stanzas). This is the reverse log from next to my current working tree:
>
> 0e7e31f DMA: PL330: use prefix in reg names to build under x86
> 1e8486a watchdog: sp805_wdt depends on ARM
> 6417077 mmc: Use the new <linux/sizes.h>
> 52b9f4e drivers/amba: add support for a PCI bridge
> d8d2313 x86: add CONFIG_ARM_AMBA, selected by STA2X11
>
> They all have the proper acked and signed-off, as well as references
> to the original mailing list message by my mate Davide who submitted
> them.
>
> Shall I just wait for you to merge or shall I repost to the mailing
> lists? In the latte case, with or without the various ack/signoff?
>
We have been waiting for you to sort out the breakages and let us know
that the problems has been resolved. Sorry, the number of email threads
have been absolutely crazy and so I have not tracked them all.
We have not been testing this branch.
What are the upstream commits?
-hpa
next prev parent reply other threads:[~2013-02-20 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 7:35 tip/x86/amba Alessandro Rubini
2013-02-20 18:08 ` H. Peter Anvin [this message]
2013-02-20 18:54 ` tip/x86/amba Alessandro Rubini
2013-02-20 19:35 ` tip/x86/amba H. Peter Anvin
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=51251101.5070008@zytor.com \
--to=hpa@zytor.com \
--cc=ciminaghi@gnudd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rubini@gnudd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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