linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-next@vger.kernel.org
Subject: Re: Fwd: Re: [PATCH] kprobes: fix compilation break due to kprobe_mutex
Date: Sun, 18 May 2008 13:53:54 +1000	[thread overview]
Message-ID: <20080518135354.d37baf4f.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080518134933.fe57718a.sfr@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

Hi Russell,

On Sun, 18 May 2008 13:49:33 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Sat, 17 May 2008 20:08:55 +0100 Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> >
> > If I'm reading this right, it's taking you about 3.5 hours to build the
> > set?
> 
> Not really, I added them in several goes and the build scripts have
> significant pauses between passes.  It also takes some time to mirror out
> the results between passes.  Tomorrow's build should be more
> representative.

It looks more like 2 hours 10 minutes or so.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-05-18  3:54 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
2008-05-18  3:49           ` Stephen Rothwell
2008-05-18  3:53             ` Stephen Rothwell [this message]

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=20080518135354.d37baf4f.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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).