From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/8] 2.6.17 merge additions
Date: Fri, 02 Mar 2007 09:05:53 +0000 [thread overview]
Message-ID: <45E7F701.76E4.0078.0@novell.com> (raw)
In-Reply-To: <45D33F3C.76E4.0078.0@novell.com>
>>> "Jan Beulich" <jbeulich@novell.com> 14.02.07 16:56 >>>
>Following will be a set of patches that adjust 2.6.17 merges we had done
>differently in our internal tree, and that I think shouldn't get lost. There
>is no particular ordering among them, so if any seems questionable, others
>can still be applied.
Before submitting 2.6.18 stuff we were missing from the -unstable merge,
is it possible to get an understanding why patches 5 (pc speaker device
registration in domU) and 8 (early DMI scan) of the 2.6.17 set were not
taken?
Thanks, Jan
next prev parent reply other threads:[~2007-03-02 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 15:56 [PATCH 0/8] 2.6.17 merge additions Jan Beulich
2007-03-02 9:05 ` Jan Beulich [this message]
2007-03-02 9:19 ` Keir Fraser
2007-03-02 9:59 ` Jan Beulich
2007-03-02 11:17 ` Keir Fraser
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=45E7F701.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--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.