All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: Boris Derzhavets <bderzhavets@yahoo.com>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: The most recent attempt to build 2.6.29-rc8
Date: Wed, 25 Mar 2009 10:28:11 -0700	[thread overview]
Message-ID: <49CA69AB.1060104@goop.org> (raw)
In-Reply-To: <alpine.GSO.2.00.0903250840210.2991@algedi.dur.ac.uk>

M A Young wrote:
> That's strange because it wasn't when I sent it. I wonder if it got 
> mangled in-transit.

It was an attachment, so it should have been resistant.  Though it also 
had a '\0' on the end for good measure.

>> Unfortunately this didn't help me; it still ended up making this 'm', 
>> which doesn't work.  The simple fix is, I think, to make this a 
>> "bool", so it gets built in.  Its not really big enough to bother with.
>
> I have been using XEN_XENBUS_FRONTEND=m on some of my kernels so it 
> didn't cause me a problem, though of course if any of the dependent 
> modules were "y" then that would indeed be incorrect. I did have an 
> alternate way of doing it that I could try. 

Hm.  I wonder if there's a bunch of symbol exports missing.  Or perhaps 
it's a secondary problem, like mkinitrd is not putting the right modules 
in place.

    J

  parent reply	other threads:[~2009-03-25 17:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 18:21 Fw: Re: tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" Boris Derzhavets
2009-03-16 18:44 ` Andrew Lyon
2009-03-16 18:51 ` Jeremy Fitzhardinge
2009-03-16 19:03   ` Boris Derzhavets
2009-03-16 19:14     ` Jeremy Fitzhardinge
2009-03-16 21:15       ` Boris Derzhavets
2009-03-20 10:25         ` Boris Derzhavets
2009-03-20 17:30           ` Boris Derzhavets
2009-03-21 17:28             ` The most recent attempt to build 2.6.29-rc8 Boris Derzhavets
2009-03-22  4:28               ` Jeremy Fitzhardinge
2009-03-22  7:02                 ` Boris Derzhavets
2009-03-22  8:16                   ` Boris Derzhavets
2009-03-22 10:16                     ` Boris Derzhavets
2009-03-22 12:32               ` M A Young
2009-03-22 14:55                 ` Boris Derzhavets
2009-03-22 15:06                   ` M A Young
2009-03-22 15:46                     ` Boris Derzhavets
2009-03-22 17:09                       ` M A Young
2009-03-22 18:03                         ` M A Young
2009-03-22 18:22                         ` Boris Derzhavets
2009-03-22 21:25                           ` M A Young
2009-03-25  8:22                             ` Jeremy Fitzhardinge
2009-03-25  8:52                               ` M A Young
2009-03-25  9:12                                 ` M A Young
2009-03-25 17:45                                   ` Jeremy Fitzhardinge
2009-03-25 18:37                                     ` Boris Derzhavets
2009-03-25 17:28                                 ` Jeremy Fitzhardinge [this message]
2009-03-16 19:14   ` Fw: Re: tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" Boris Derzhavets

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=49CA69AB.1060104@goop.org \
    --to=jeremy@goop.org \
    --cc=bderzhavets@yahoo.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.