From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 01/10] xen: xenbus: quirk uses x86 specific cpuid
Date: Wed, 17 Oct 2012 10:56:02 -0400 [thread overview]
Message-ID: <20121017145602.GB7594@phenom.dumpdata.com> (raw)
In-Reply-To: <507E91E602000078000A1E76@nat28.tlf.novell.com>
On Wed, Oct 17, 2012 at 10:09:26AM +0100, Jan Beulich wrote:
> >>> On 17.10.12 at 10:39, Ian Campbell <ian.campbell@citrix.com> wrote:
> > --- a/drivers/xen/xenbus/xenbus_xs.c
> > +++ b/drivers/xen/xenbus/xenbus_xs.c
> > @@ -619,6 +619,8 @@ static struct xenbus_watch *find_watch(const char *token)
> >
> > return NULL;
> > }
> > +
> > +#ifdef CONFIG_X86
> > /*
> > * Certain older XenBus toolstack cannot handle reading values that are
> > * not populated. Some Xen 3.4 installation are incapable of doing this
> > @@ -637,6 +639,10 @@ static bool xen_strict_xenbus_quirk()
> > return false;
> >
> > }
> > +#else
> > +static bool xen_strict_xenbus_quirk(void) { return false; }
> > +#endif
>
> Wouldn't it reduce redundancy if the #ifdef block was inserted
> inside the existing function?
Applied with Jan's suggestions.
>
> Jan
>
> > +
> > static void xs_reset_watches(void)
> > {
> > int err, supported = 0;
>
next prev parent reply other threads:[~2012-10-17 14:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1350463138.2460.19.camel@zakaz.uk.xensource.com>
2012-10-17 8:39 ` [PATCH 01/10] xen: xenbus: quirk uses x86 specific cpuid Ian Campbell
2012-10-17 8:41 ` Ian Campbell
2012-10-17 9:09 ` Jan Beulich
2012-10-17 14:56 ` Konrad Rzeszutek Wilk [this message]
2012-10-17 8:39 ` [PATCH 02/10] xen: sysfs: include err.h for PTR_ERR etc Ian Campbell
2012-10-17 16:59 ` Stefano Stabellini
2012-10-17 8:39 ` [PATCH 03/10] xen: sysfs: fix build warning Ian Campbell
2012-10-17 17:02 ` Stefano Stabellini
2012-10-18 7:32 ` Ian Campbell
2012-10-17 8:39 ` [PATCH 04/10] xen: dbgp: Fix warning when CONFIG_PCI is not enabled Ian Campbell
2012-10-17 9:10 ` Jan Beulich
2012-10-17 17:08 ` Stefano Stabellini
2012-10-17 8:39 ` [PATCH 05/10] xen: events: pirq_check_eoi_map is X86 specific Ian Campbell
2012-10-17 17:06 ` Stefano Stabellini
2012-10-18 7:29 ` Ian Campbell
2012-10-17 8:39 ` [PATCH 06/10] xen: XENMEM_translate_gpfn_list was remove ages ago and is unused Ian Campbell
2012-10-17 8:39 ` [PATCH 07/10] xen: grant: use xen_pfn_t type for frame_list Ian Campbell
2012-10-17 17:10 ` Stefano Stabellini
2012-10-17 8:39 ` [PATCH 08/10] xen: balloon: don't include e820.h Ian Campbell
2012-10-17 17:35 ` Stefano Stabellini
2012-10-17 8:39 ` [PATCH 09/10] xen: balloon: use correct type for frame_list Ian Campbell
2012-10-17 17:28 ` Stefano Stabellini
2012-10-17 17:32 ` Konrad Rzeszutek Wilk
2012-10-18 7:26 ` Ian Campbell
2012-10-17 8:39 ` [PATCH 10/10] xen: arm: make p2m operations NOPs Ian Campbell
2012-10-17 17:13 ` Stefano Stabellini
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=20121017145602.GB7594@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).