From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen 3.1.3 and Linux Kernel 2.6.18.8
Date: Wed, 16 Jan 2008 16:50:54 +0200 [thread overview]
Message-ID: <200801161650.58395.caglar@pardus.org.tr> (raw)
In-Reply-To: <C3B3C40A.1ADB3%Keir.Fraser@cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 682 bytes --]
Hi;
16 Oca 2008 Çar tarihinde, Keir Fraser şunları yazmıştı:
> Is this the *only* change in the .8 patch that affects any sparse tree
> file?
>
> -- Keir
I'll check again ASAP, by the way what i do is like that, if its wrong please
yell.
First i use 2.6.18 as a base with current sparse tree and generate a Xen
patches tree.
After that, i tried to patch this tree with 2.6.18.8 patch and check .rej
files against sparse tree history to decide whether its needed or not etc.
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-01-16 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 19:32 Xen 3.1.3 and Linux Kernel 2.6.18.8 Joshua West
2008-01-15 21:12 ` Keir Fraser
2008-01-16 12:56 ` S.Çağlar Onur
2008-01-16 13:22 ` Keir Fraser
2008-01-16 13:25 ` S.Çağlar Onur
2008-01-16 13:41 ` Keir Fraser
2008-01-16 13:58 ` Keir Fraser
2008-01-16 14:22 ` S.Çağlar Onur
2008-01-16 14:24 ` Keir Fraser
2008-01-16 14:50 ` S.Çağlar Onur [this message]
2008-01-16 15:02 ` Ian Campbell
2008-01-16 16:22 ` S.Çağlar Onur
2008-01-15 21:41 ` S.Çağlar Onur
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=200801161650.58395.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=Keir.Fraser@cl.cam.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.