From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Steve Cotton <steve@s.cotton.clara.co.uk>
Subject: Re: Commit 9a11899 (USB: OHCI: add missing PCI PM callbacks to ohci-pci.c) breaks several builds
Date: Sun, 25 Aug 2013 21:26:53 -0700 [thread overview]
Message-ID: <20130826042653.GA2778@kroah.com> (raw)
In-Reply-To: <521AD347.1090601@roeck-us.net>
On Sun, Aug 25, 2013 at 09:02:15PM -0700, Guenter Roeck wrote:
> On 08/25/2013 08:30 PM, Guenter Roeck wrote:
> > Broken builds:
> > mips:ath79_defconfig
> > parisc:defconfig
> > sparc32:defconfig
> > sparc64:defconfig
> > tile:defconfig
> >
> Add:
> powerpc:ppc64e_defconfig
> powerpc:cell_defconfig
> powerps:maple_defconfig
>
> That makes it 8 out of 82 builds, or roughly 10% of all builds.
>
> My qemu test build for powerpc (which has its own config file) fails as well :(.
Ugh, I got no reports of this from linux-next or the 0-day build system,
odd.
Alan, can you send a follow-on patch to fix this?
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-26 4:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 3:30 Commit 9a11899 (USB: OHCI: add missing PCI PM callbacks to ohci-pci.c) breaks several builds Guenter Roeck
2013-08-26 4:02 ` Guenter Roeck
2013-08-26 4:26 ` Greg Kroah-Hartman [this message]
2013-08-26 4:56 ` Guenter Roeck
2013-08-26 14:47 ` Alan Stern
2013-08-26 14:53 ` [PATCH] USB: OHCI: fix build error related to ohci_suspend/resume Alan Stern
2013-08-26 15:38 ` Greg Kroah-Hartman
2013-08-26 16:06 ` Guenter Roeck
2013-08-26 16:50 ` Greg Kroah-Hartman
2013-08-26 17:19 ` Guenter Roeck
2013-08-26 22:14 ` Greg Kroah-Hartman
2013-08-26 22:23 ` Guenter Roeck
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=20130826042653.GA2778@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=stern@rowland.harvard.edu \
--cc=steve@s.cotton.clara.co.uk \
--cc=torvalds@linux-foundation.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