From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: xen-compat.h vs 4.5
Date: Wed, 14 Jan 2015 11:31:01 +0000 [thread overview]
Message-ID: <1421235061.19103.224.camel@citrix.com> (raw)
In-Reply-To: <54B654CF0200007800054B19@mail.emea.novell.com>
(CCing Konrad==RM)
On Wed, 2015-01-14 at 10:36 +0000, Jan Beulich wrote:
> All,
>
> while we don't have any changes in the public interface depending on
> __XEN_INTERFACE_VERSION__ <relation> 0x00040500, shouldn't
> we nevertheless update xen-compat.h's
> __XEN_LATEST_INTERFACE_VERSION__ for 4.5?
We probably should have done, but I think it is too late now unless we
think we could justify force pushing such a change, which I doubt.
I think it's a bit of a tree falling in the woods change anyway, if
there are no relevant changes would anyone notice if it remained at 4.4?
Perhaps for 4.5.1? (But it doesn't sound entirely stable release
material too me...)
Ian.
next prev parent reply other threads:[~2015-01-14 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 10:36 xen-compat.h vs 4.5 Jan Beulich
2015-01-14 11:31 ` Ian Campbell [this message]
2015-01-14 11:43 ` Jan Beulich
2015-01-14 18:52 ` Konrad Rzeszutek Wilk
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=1421235061.19103.224.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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.