linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: Fwd: Re: [PATCH] kprobes: fix compilation break due to kprobe_mutex
Date: Sat, 17 May 2008 20:08:55 +0100	[thread overview]
Message-ID: <20080517190855.GC13933@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080518022010.56a8bf46.sfr@canb.auug.org.au>

On Sun, May 18, 2008 at 02:20:10AM +1000, Stephen Rothwell wrote:
> On Sat, 17 May 2008 23:59:26 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Sat, 17 May 2008 14:35:27 +0100 Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> > >
> > > The answer is all of them.  I can't suggest any subset, mainly because
> > > I don't know what's in each and what each will cover.  The coverage of
> > > each is really up to each platform maintainer I'm afraid.
> > 
> > OK, I will see what happens if I add them all.  You may need to ping me
> > if any get added or removed.
> 
> I have added them all.  There are some results on the web page already
> (http://kisskb.ellerman.id.au/kisskb/compiler/11/) which are all ok.  On
> our internal page (which will be mirrored above in an hour or so) there
> are some failures (so far clps7500_defconfig, collie_defconfig,
> corgi_defconfig, eseries_pxa_defconfig and magician_defconfig). Check
> there later.

If I'm reading this right, it's taking you about 3.5 hours to build the
set?

spitz_defconfig - trivial fix (I'll push that with my upcoming set)
magican_defconfig - ditto
omap*_defconfig - hopefully my recent merge of fixes from Tony Lindgren
 should resolve this.
eseries_pxa_defconfig - looks like a botched defconfig file ;(
corgi_defconfig - tried to get the person concerned to submit a trivial
 patch but wants to introduce some infrastructure instead
clps7500_defconfig - you may as well disable, I'll probably eventually
 remove this platform.

Lastly, collie_defconfig seems to be broken as a result of 5025/1 -
which claims to be a "fix" patch but is actually a "break" patch. ;(

Thanks.

  reply	other threads:[~2008-05-17 19:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-17 11:42 Fwd: Re: [PATCH] kprobes: fix compilation break due to kprobe_mutex Russell King - ARM Linux
2008-05-17 12:02 ` Stephen Rothwell
2008-05-17 12:17   ` Stephen Rothwell
2008-05-17 13:35   ` Russell King - ARM Linux
2008-05-17 13:59     ` Stephen Rothwell
2008-05-17 16:20       ` Stephen Rothwell
2008-05-17 19:08         ` Russell King - ARM Linux [this message]
2008-05-18  3:49           ` Stephen Rothwell
2008-05-18  3:53             ` Stephen Rothwell

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=20080517190855.GC13933@flint.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).