All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: preparing for 4.2.2 and 4.1.5
Date: Tue, 12 Mar 2013 12:57:55 +0100	[thread overview]
Message-ID: <513F1843.90202@invisiblethingslab.com> (raw)
In-Reply-To: <1363089303.29599.11.camel@zakaz.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1295 bytes --]

On 12.03.2013 12:55, Ian Campbell wrote:
> On Sun, 2013-03-10 at 22:53 +0000, Marek Marczykowski wrote:
>> On 27.02.2013 17:12, Jan Beulich wrote:
>>> Aiming at a release towards the end of March, I'd like to cut RC1-s
>>> at the beginning of next week.
>>>
>>> Please indicate any bug fixes that so far may have been missed
>>> in the backports already done. Quite a few fixes are currently
>>> stuck in master's staging branch - these don't need to be named
>>> explicitly, I'm already planning to pull over the hypervisor ones
>>> as soon as they get out of staging (and I'm sure Ian is planning
>>> the same - if applicable at all - for the tools side).
>>>
>>> Ian - one thing I think is still open for 4.1.5 is the xz kernel
>>> decompression support that was explicitly requested on the list.
>>> Can this be expected to go in for RC1?
>>
>> I'd like "libxc: do not "panic" if a kernel is not a bzImage." [1] to be
>> backported to xen-4.1
> 
> I think this is a purely cosmetic fix? Not that I mind but that should
> be taken into consideration.

Yes, but annoying one. Especially it causes confusing error message when
starting HVM with stubdom (only message, doesn't break start).

-- 
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 553 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-03-12 11:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 16:12 preparing for 4.2.2 and 4.1.5 Jan Beulich
2013-02-27 18:44 ` Alex Bligh
2013-02-28  7:31   ` Jan Beulich
2013-02-28  9:21     ` Alex Bligh
2013-02-28  9:32       ` Jan Beulich
2013-02-28 12:40         ` Stefano Stabellini
2013-02-28 18:31           ` Alex Bligh
2013-02-28 10:18 ` M A Young
2013-02-28 11:49   ` Ian Jackson
2013-02-28 15:31 ` Egger Christoph
2013-02-28 15:44   ` Jan Beulich
2013-03-01 15:23 ` Andrew Cooper
2013-03-01 15:39   ` Jan Beulich
2013-03-06 18:14 ` Andrew Cooper
2013-03-08  9:57   ` Jan Beulich
2013-03-08 11:18     ` Andrew Cooper
2013-03-08 12:01 ` Andrew Cooper
2013-03-08 12:53   ` Jan Beulich
2013-03-08 13:01 ` Jan Beulich
2013-03-10 22:53 ` Marek Marczykowski
2013-03-12 11:55   ` Ian Campbell
2013-03-12 11:57     ` Marek Marczykowski [this message]
2013-03-11 11:36 ` Alex Bligh
2013-03-11 13:35   ` Jan Beulich
2013-03-19  7:50 ` preparing for 4.2.2 and 4.1.5 / libxl blktap2 patch Pasi Kärkkäinen
2013-03-27  9:52   ` Pasi Kärkkäinen

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=513F1843.90202@invisiblethingslab.com \
    --to=marmarek@invisiblethingslab.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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.