xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] stubdom: fix errors in newlib
Date: Tue, 10 Jul 2012 20:02:11 +0200	[thread overview]
Message-ID: <20120710180211.GA20075@aepfle.de> (raw)
In-Reply-To: <1341939543.8586.75.camel@hastur.hellion.org.uk>

On Tue, Jul 10, Ian Campbell wrote:

> On Tue, 2012-07-10 at 12:12 -0400, Olaf Hering wrote:
> > # HG changeset patch
> > # User Olaf Hering <olaf@aepfle.de>
> > # Date 1341839122 -7200
> > # Node ID 2dd50c201ca0d3542f3589942ae9e51d33ec7509
> > # Parent  42f76d536b116d2ebad1b6705ae51ecd171d2581
> > stubdom: fix errors in newlib
> > 
> > rpmlint found a few code bugs in newlib, and marks them as errors after
> > rpm build. Add another newlib patch and apply it during stubdom build.
> 
> Are any of these specific to Xen or should they really be being sent to
> newlib upstream? (we could really do with resyncing on he latest newlib
> and sending or our patches again it. In our CFT of course ;-))

I have not yet checked wether upstream has the same issue, just trying
to fix the build errors.

Olaf

  reply	other threads:[~2012-07-10 18:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 16:12 [PATCH] stubdom: fix errors in newlib Olaf Hering
2012-07-10 16:59 ` Ian Campbell
2012-07-10 18:02   ` Olaf Hering [this message]
2012-07-10 20:51   ` Olaf Hering
2012-07-12  7:56   ` Olaf Hering
2012-07-24 14:47     ` [PATCH] stubdom: fix errors in newlib [and 1 more messages] Ian Jackson
2012-07-24 14:48       ` Ian Campbell
2012-07-24 14:49         ` Ian Jackson
2012-07-30 18:44       ` Olaf Hering
2012-07-30 18:45         ` Ian Campbell

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=20120710180211.GA20075@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=ian.campbell@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 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).