All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	M A Young <m.a.young@durham.ac.uk>
Subject: Re: Three small patches for xen-4.1.0-rc
Date: Tue, 1 Feb 2011 19:21:39 +0000	[thread overview]
Message-ID: <19784.23875.216246.78463@mariner.uk.xensource.com> (raw)
In-Reply-To: <1296552004.13091.11.camel@zakaz.uk.xensource.com>

Ian Campbell writes ("Re: [Xen-devel] Three small patches for xen-4.1.0-rc"):
> On Mon, 2011-01-31 at 22:37 +0000, M A Young wrote:
> > Here are three small patches that I have applied to the Fedora xen builds 
> > and I think are are suitable for xen-4.1.0.

Thanks, I have applied them.

> Thanks, I general we would prefer separate patches to be submitted
> separately rather than bundled in a single submission ("hg email" can
> help with this for large series).

I agree with Ian's comments.

> > The next patch updates a comment about NetworkManager not supporting 
> > bridging in Fedora 11 to refer instead to Fedora 14.
> 
> Was the NetworkManager stuff introduced in 14 and erroneously documented
> as being in 11, or was it in 11 and worked fine, or has it been
> continuously broken since F11? IOW should this comment refer to breakage
> in Fedora 11 thru 14 or something similar?

Perhaps you misread the document ?  I don't think NetworkManager can
set up a bridge at all.  So you just have to disable NetworkManager.
I clarified the wording slightly while applying the patch.

> > The final patch solve a build problem in Fedora rawhide, where rpm (4.9.0) 
> > doesn't automatically supply a "provides" entry for a library unless it is 
> > executable. This patch makes the libvhd and libblktap library files 
> > executable (and consistent with the other libraries in xen) so that rpm 
> > generates the right "provides" entries and therefore does the right thing 
> > when resolving package dependencies.
> 
> Ick, but apparently normal.

Shared libraries are indeed supposed to be executable.  This isn't the
only thing that can go wrong if they aren't.

Thanks,
Ian.

      parent reply	other threads:[~2011-02-01 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 22:37 Three small patches for xen-4.1.0-rc M A Young
2011-02-01  9:20 ` Ian Campbell
2011-02-01 18:29   ` M A Young
2011-02-01 19:21   ` Ian Jackson [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=19784.23875.216246.78463@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=m.a.young@durham.ac.uk \
    --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.