From: Alex Williamson <alex.williamson@hp.com>
To: Simon Horman <horms@verge.net.au>
Cc: xen-devel <xen-devel@lists.xensource.com>,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: [Xen-ia64-devel] Re: [ANNOUNCE] Second release candidate for 3.1.2
Date: Fri, 02 Nov 2007 19:33:22 -0600 [thread overview]
Message-ID: <1194053602.31834.126.camel@bling> (raw)
In-Reply-To: <20071103011351.GA4199@verge.net.au>
On Sat, 2007-11-03 at 10:13 +0900, Simon Horman wrote:
> On Fri, Nov 02, 2007 at 11:00:40AM -0600, Alex Williamson wrote:
> > On Fri, 2007-11-02 at 15:08 +0000, Keir Fraser wrote:
> > > I've ended up with enough new patches in the 3.1-testing tree, and in
> > > particular the fixes to debug-register handling are fairly extensive, so it
> > > makes sense to roll another release candidate for 3.1.2. I expect to release
> > > this as 3.1.2 final next week if there are no horrors lurking.
> >
> > RC2 looks good in my testing. CC'd xen-ia64-devel for more coverage.
> > Thanks,
>
> Should we turn off KEXEC and friends in the ia64 default configs as its not
> ready yet ? Basically reversing cb1c72a8f273 for now.
I don't see that they're on, note that this is 3.1.2, not 3.2. See
here for the tree: http://xenbits.xensource.com/xen-3.1-testing.hg
Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
next prev parent reply other threads:[~2007-11-03 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 15:08 [ANNOUNCE] Second release candidate for 3.1.2 Keir Fraser
2007-11-02 17:00 ` Alex Williamson
2007-11-03 1:13 ` [Xen-ia64-devel] " Simon Horman
2007-11-03 1:33 ` Alex Williamson [this message]
2007-11-05 1:37 ` Simon Horman
2007-11-06 6:46 ` [Xen-devel] Re: Re: [ANNOUNCE] Second releasecandidate " Yang, Liuqing
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=1194053602.31834.126.camel@bling \
--to=alex.williamson@hp.com \
--cc=horms@verge.net.au \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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.