All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
To: xen-devel@lists.xensource.com
Subject: upgrade 2.6.12 - testing wanted
Date: Thu, 7 Jul 2005 20:34:39 +0200	[thread overview]
Message-ID: <20050707183439.GA17172@snarc.org> (raw)

Hi,

we are going to upgrade very soon the repository to 2.6.12.
meanwhile I'ld appreciate if some people could test the patch, and see
if there's no regressions or anything bad before everybody get to use it.

just get latest snapshot of unstable, then do:

mv linux-2.6.11-xen-sparse/ linux-2.6.12-xen-sparse/
mv patches/linux-2.6.11/ patches/linux-2.6.12/
rm patches/linux-2.6.12/agpgart.patch
rm patches/linux-2.6.12/i386-cpu-hotplug-updated-for-mm.patch
rm patches/linux-2.6.12/iomap.patch
rm patches/linux-2.6.12/linux-2.6.11.12.patch
rm patches/linux-2.6.12/udp-frag.patch

get the patch here:

http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/temp/xen-upgrade-2612-rc2.diff.bz2

and apply it on top of your repository.

Cheers,
-- 
Vincent Hanquez

             reply	other threads:[~2005-07-07 18:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 18:34 Vincent Hanquez [this message]
2005-07-07 19:12 ` upgrade 2.6.12 - testing wanted Andrew Theurer
2005-07-07 19:30 ` Andrew Theurer
2005-07-07 19:53   ` Paul Larson
2005-07-07 20:06     ` Andrew Theurer
2005-07-07 20:29       ` Paul Larson
2005-07-07 23:02       ` [PATCH] fix CONFIG_CPU_HOTPLUG compile with 2.6.12 upgrade Ryan Harper
2005-07-08  0:12         ` David Hopwood
2005-07-07 21:12   ` upgrade 2.6.12 - testing wanted Ryan Harper
2005-07-08 16:04   ` Vincent Hanquez
2005-07-08  1:43 ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2005-07-08  3:08 Li, Xin B
2005-07-08  5:39 ` Chris Wright

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=20050707183439.GA17172@snarc.org \
    --to=vincent.hanquez@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.