[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] make mkpatches


  • To: "Chris Wright" <chrisw@xxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Fri, 23 Sep 2005 12:01:39 +1000
  • Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 23 Sep 2005 01:59:24 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcW/4mHwbFgn7I5iR6i1ZOCtV8k+4wAABaLg
  • Thread-topic: [Xen-devel] make mkpatches

> -----Original Message-----
> From: Chris Wright [mailto:chrisw@xxxxxxxx]
> Sent: Friday, 23 September 2005 11:59
> To: James Harper
> Cc: Chris Wright; Xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] make mkpatches
> 
> * James Harper (james.harper@xxxxxxxxxxxxxxxx) wrote:
> > >
> > > Sounds like you're not picking up the patches that get applied to
the
> > > base tree from patches/linux-2.6.12/  (btw, the smp_alts.patch
won't
> > > compile on plain x86, it's missing a trivial fix).
> >
> > That sounds plausible. I assumed that mkpatches would do this.
Should I
> > apply these patches/linux-2.6.12/* before or after applying the
> > mkpatches-generated patch?
> 
> Apply them before the mkpatches patch.

I tried them the other way around and it worked too. I guess the patches
don't tread on each other much. The mkpatches patch said it should be
applied to a pristine kernel tree.

It seems to be compiling now. Quite a few 'implicit declaration of
function ...' and '... is deprecated' warnings, but no errors so far.
Thanks.

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.