All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
	"xen.org" <ian.jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [xen-unstable test] 4473: regressions - FAIL
Date: Fri, 24 Dec 2010 10:56:44 +0000	[thread overview]
Message-ID: <C93A2CEC.F533%keir@xen.org> (raw)
In-Reply-To: <1293187507.22419.164.camel@zakaz.uk.xensource.com>

On 24/12/2010 10:45, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:

> On Fri, 2010-12-24 at 10:37 +0000, xen.org wrote:

> 
> 64 bit failures are the libxc issue I posted a patch for just now.
> 
> 32 bit failures are:
>         cc1: warnings being treated as errors
>         sched_credit2.c: In function 'csched_dump':
>         sched_credit2.c:1790: error: format '%3ld' expects type 'long int',
> but argument 6 has type 's_time_t'

Applied your fix to xen-unstable staging.

 Thanks,
 Keir

> Requiring:
> 
> diff -r a4369aa8ab41 xen/common/sched_credit2.c
> --- a/xen/common/sched_credit2.c Fri Dec 24 09:47:12 2010 +0000
> +++ b/xen/common/sched_credit2.c Fri Dec 24 10:45:03 2010 +0000
> @@ -1782,7 +1782,7 @@ csched_dump(const struct scheduler *ops)
>                 "\tncpus              = %u\n"
>                 "\tmax_weight         = %d\n"
>                 "\tinstload           = %d\n"
> -               "\taveload            = %3ld\n",
> +               "\taveload            = %3"PRI_stime"\n",
>                 i,
>                 cpus_weight(prv->rqd[i].active),
>                 prv->rqd[i].max_weight,
> 
> Ian.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-12-24 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24 10:37 [xen-unstable test] 4473: regressions - FAIL xen.org
2010-12-24 10:45 ` Ian Campbell
2010-12-24 10:56   ` Keir Fraser [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=C93A2CEC.F533%keir@xen.org \
    --to=keir@xen.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.