From: Frederico Cadete <frederico@cadete.eu>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 2] xmem/tmem: fix 'undefined variable' build error.
Date: Tue, 28 May 2013 16:39:33 +0200 [thread overview]
Message-ID: <20130528143933.GA6597@qspin.be> (raw)
In-Reply-To: <20130528135321.GH724@phenom.dumpdata.com>
On Tue, May 28, 2013 at 09:53:21AM -0400, Konrad Rzeszutek Wilk wrote:
> You are missing an Signed-off-by here. Are you OK affixing it here?
>
Sorry, my bad. And checkpatch warned me about that...
A fixed version of the patch follows below. Thanks for being so patient.
Regards,
Frederico
From: Frederico Cadete <frederico@cadete.eu>
Date: Tue, 28 May 2013 16:19:49 +0200
Subject: [PATCH 2] xmem/tmem: fix 'undefined variable' build error.
In the (not so useful) kernel configuration where CONFIG_SWAP
is undefined and CONFIG_XEN_SELFBALLOONING is defined,
xen_tmem_init would use undefined variable 'static bool frontswap'.
Added #else to have #define frontswap (0) in the case where
CONFIG_FRONTSWAP is not defined.
Signed-off-by: Frederico Cadete <frederico@cadete.eu>
---
drivers/xen/tmem.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/xen/tmem.c b/drivers/xen/tmem.c
index 18e8bd8..cc072c6 100644
--- a/drivers/xen/tmem.c
+++ b/drivers/xen/tmem.c
@@ -41,6 +41,8 @@ module_param(selfballooning, bool, S_IRUGO);
#ifdef CONFIG_FRONTSWAP
static bool frontswap __read_mostly = true;
module_param(frontswap, bool, S_IRUGO);
+#else /* CONFIG_FRONTSWAP */
+#define frontswap (0)
#endif /* CONFIG_FRONTSWAP */
#ifdef CONFIG_XEN_SELFBALLOONING
--
1.7.9.5
prev parent reply other threads:[~2013-05-28 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130525204842.GA8844@gmail.com>
2013-05-28 13:53 ` [PATCH 2] xmem/tmem: fix 'undefined variable' build error Konrad Rzeszutek Wilk
2013-05-28 14:39 ` Frederico Cadete [this message]
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=20130528143933.GA6597@qspin.be \
--to=frederico@cadete.eu \
--cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).