From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel <xen-devel@lists.xen.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen: constify all instances of "struct attribute_group"
Date: Sun, 26 Feb 2012 11:02:30 -0500 [thread overview]
Message-ID: <20120226160230.GA2274@phenom.dumpdata.com> (raw)
In-Reply-To: <4F4786FD0200007800074A0C@nat28.tlf.novell.com>
On Fri, Feb 24, 2012 at 11:47:57AM +0000, Jan Beulich wrote:
> The functions these get passed to have been taking pointers to const
> since at least 2.6.16.
What is this based on? I get:
HEAD is now at b01543d... Linux 3.3-rc4
konrad@phenom:~/ssd/linux$ patch -p1 < /tmp/jan-1
patching file drivers/xen/sys-hypervisor.c
Hunk #1 FAILED at 97.
Hunk #2 FAILED at 210.
Hunk #3 FAILED at 340.
3 out of 3 hunks FAILED -- saving rejects to file drivers/xen/sys-hypervisor.c.rej
patching file drivers/xen/xen-balloon.c
Hunk #1 FAILED at 207.
1 out of 1 hunk FAILED -- saving rejects to file drivers/xen/xen-balloon.c.rej
patching file drivers/xen/xen-selfballoon.c
Hunk #1 FAILED at 488.
1 out of 1 hunk FAILED -- saving rejects to file drivers/xen/xen-selfballoon.c.rej
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> ---
> drivers/xen/sys-hypervisor.c | 6 +++---
> drivers/xen/xen-balloon.c | 2 +-
> drivers/xen/xen-selfballoon.c | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> --- 3.3-rc4/drivers/xen/sys-hypervisor.c
> +++ 3.3-rc4-xen-const-attribute_group/drivers/xen/sys-hypervisor.c
> @@ -97,7 +97,7 @@ static struct attribute *version_attrs[]
> NULL
> };
>
> -static struct attribute_group version_group = {
> +static const struct attribute_group version_group = {
> .name = "version",
> .attrs = version_attrs,
> };
> @@ -210,7 +210,7 @@ static struct attribute *xen_compile_att
> NULL
> };
>
> -static struct attribute_group xen_compilation_group = {
> +static const struct attribute_group xen_compilation_group = {
> .name = "compilation",
> .attrs = xen_compile_attrs,
> };
> @@ -340,7 +340,7 @@ static struct attribute *xen_properties_
> NULL
> };
>
> -static struct attribute_group xen_properties_group = {
> +static const struct attribute_group xen_properties_group = {
> .name = "properties",
> .attrs = xen_properties_attrs,
> };
> --- 3.3-rc4/drivers/xen/xen-balloon.c
> +++ 3.3-rc4-xen-const-attribute_group/drivers/xen/xen-balloon.c
> @@ -207,7 +207,7 @@ static struct attribute *balloon_info_at
> NULL
> };
>
> -static struct attribute_group balloon_info_group = {
> +static const struct attribute_group balloon_info_group = {
> .name = "info",
> .attrs = balloon_info_attrs
> };
> --- 3.3-rc4/drivers/xen/xen-selfballoon.c
> +++ 3.3-rc4-xen-const-attribute_group/drivers/xen/xen-selfballoon.c
> @@ -488,7 +488,7 @@ static struct attribute *selfballoon_att
> NULL
> };
>
> -static struct attribute_group selfballoon_group = {
> +static const struct attribute_group selfballoon_group = {
> .name = "selfballoon",
> .attrs = selfballoon_attrs
> };
>
>
next prev parent reply other threads:[~2012-02-26 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 11:47 [PATCH] xen: constify all instances of "struct attribute_group" Jan Beulich
2012-02-26 16:02 ` Konrad Rzeszutek Wilk [this message]
2012-02-27 8:27 ` Jan Beulich
2012-03-14 16:35 ` [Xen-devel] " 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=20120226160230.GA2274@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox