From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Tim Deegan <tim@xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 3/3] xen/init: Annotate all command line parameter infrastructure as const
Date: Mon, 22 Feb 2016 09:36:14 -0700 [thread overview]
Message-ID: <56CB470E02000078000D4DBA@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1454951267-30034-3-git-send-email-andrew.cooper3@citrix.com>
>>> On 08.02.16 at 18:07, <andrew.cooper3@citrix.com> wrote:
> There is no reason for any of it to be modified. Additionally, link
> .init.setup beside the other constant .init data.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Sadly I've noticed only after pushing that this breaks the build
with older gcc. 4.3.4 complains about a section type conflict in
mwait-idle.c. I've reverted the change for the time being.
Jan
next prev parent reply other threads:[~2016-02-22 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 17:07 [PATCH 1/3] xen/x86: Drop the uses of invbool_param() Andrew Cooper
2016-02-08 17:07 ` [PATCH 2/3] xen/init: Drop invbool_param() Andrew Cooper
2016-02-09 12:47 ` Jan Beulich
2016-02-08 17:07 ` [PATCH 3/3] xen/init: Annotate all command line parameter infrastructure as const Andrew Cooper
2016-02-09 12:43 ` Jan Beulich
2016-02-09 13:52 ` Andrew Cooper
2016-02-09 14:32 ` Jan Beulich
2016-02-09 14:40 ` Andrew Cooper
2016-02-09 14:50 ` Jan Beulich
2016-02-22 16:36 ` Jan Beulich [this message]
2016-02-22 16:41 ` Andrew Cooper
2016-02-22 18:43 ` Doug Goldstein
2016-02-23 8:07 ` Jan Beulich
2016-02-09 12:46 ` [PATCH 1/3] xen/x86: Drop the uses of invbool_param() Jan Beulich
2016-02-11 9:58 ` Ian Campbell
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=56CB470E02000078000D4DBA@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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.