All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Alessandro Rubini <rubini@gnudd.com>,
	linux-kernel@vger.kernel.org, giancarlo.asnaghi@st.com,
	ciminaghi@gnudd.com, alan@linux.intel.com, tglx@linutronix.de,
	mingo@redhat.com, x86@kernel.org
Subject: Re: [PATCH V5 4/5] drivers/amba: add support for a PCI bridge
Date: Wed, 20 Feb 2013 15:37:59 -0800	[thread overview]
Message-ID: <51255E57.2010803@zytor.com> (raw)
In-Reply-To: <20130220233532.GY17833@n2100.arm.linux.org.uk>

On 02/20/2013 03:35 PM, Russell King - ARM Linux wrote:
> On Wed, Feb 20, 2013 at 02:50:17PM -0800, H. Peter Anvin wrote:
>> On 02/20/2013 02:45 PM, Alessandro Rubini wrote:
>>> [meanwhile I posted V6 with the acked-by of linusw and others, that
>>> were missing in V5]
>>>
>>> rmk:
>>>>> I'm happy to take it through my tree if everyone is now happy with this.
>>>
>>> hpa: 
>>>> I am okay with that, although I would like to make sure we do a bunch of
>>>> x86 randconfigs on it before pushing it to Linus.
>>>
>>> I did like this:
>>>   - disable STA2X11 (and thus AMBA) and build
>>>   - enable STA2X11, answer y to all new questions and build
>>>
>>> So there's nothing left (you'll have two unrelated warnings, that I'm
>>> working on and I'll post a fix tomorrow).  Sure, Peter, first time I
>>> didn't do that test and missed some of the drivers.
>>>
>>
>> I was just concerned that rmk wouldn't necessarily do those tests as a
>> matter of process.
>>
>> So Russell -- how do you want to handle this?  Should I take them (and
>> ask Ingo to put them through his test machinery) or do you want to (and
>> run x86 randconfigs as part of your testing)?
> 
> Well, I'm happy to take the non-x86 bits if that's what others want (for
> the _next_ merge window, not this one.)  That _should_ result in x86 not
> seeing this stuff until it gets the ARM_AMBA definition enabled, and
> giving it a full cycle of testing.
> 
> However, if we want to keep the patch set together and route it via
> another tree, I'm also fine with that too.
> 

Actually, between linux-next and Fengguang's zeroday testbot I suspect
we'll get all the coverage we need.  So yes, go ahead and take them.

Acked-by: H. Peter Anvin <hpa@linux.intel.com>

	-hpa


  reply	other threads:[~2013-02-20 23:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 21:22 [PATCH V5 0/5] x86: a bridge from PCI to AMBA Alessandro Rubini
2013-02-20 21:23 ` [PATCH V5 1/5] DMA: PL330: use prefix in reg names to build under x86 Alessandro Rubini
2013-02-20 21:23 ` [PATCH V5 2/5] watchdog: sp805_wdt depends on ARM Alessandro Rubini
2013-02-20 21:23 ` [PATCH V5 3/5] mmc: Use the new <linux/sizes.h> Alessandro Rubini
2013-02-20 21:24 ` [PATCH V5 4/5] drivers/amba: add support for a PCI bridge Alessandro Rubini
2013-02-20 22:24   ` Russell King - ARM Linux
2013-02-20 22:33     ` H. Peter Anvin
2013-02-20 22:45       ` Alessandro Rubini
2013-02-20 22:50         ` H. Peter Anvin
2013-02-20 23:35           ` Russell King - ARM Linux
2013-02-20 23:37             ` H. Peter Anvin [this message]
2013-02-20 21:24 ` [PATCH V5 5/5] x86: add CONFIG_ARM_AMBA, selected by STA2X11 Alessandro Rubini
2013-02-20 21:58 ` [PATCH V5 0/5] x86: a bridge from PCI to 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=51255E57.2010803@zytor.com \
    --to=hpa@zytor.com \
    --cc=alan@linux.intel.com \
    --cc=ciminaghi@gnudd.com \
    --cc=giancarlo.asnaghi@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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 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.