From: Thomas Huth <thuth@redhat.com>
To: Daniel Axtens <dja@axtens.net>, linuxppc-dev@ozlabs.org
Cc: mikey@neuling.org, imunsie@au.ibm.com
Subject: Re: [PATCH] cxl: Fix ambiguous else warnings
Date: Fri, 31 Jul 2015 11:28:24 +0200 [thread overview]
Message-ID: <55BB3FB8.9010606@redhat.com> (raw)
In-Reply-To: <1438324508-30341-1-git-send-email-dja@axtens.net>
On 31/07/15 08:35, Daniel Axtens wrote:
> Every time I build cxl I see the following warnings:
>
> /scratch/dja/linux-capi/drivers/misc/cxl/pci.c: In function ‘sanitise_afu_regs’:
> /scratch/dja/linux-capi/drivers/misc/cxl/pci.c:712:6: warning: suggest explicit braces to avoid ambiguous ‘else’ [-Wparentheses]
> if (reg & CXL_PSL_DSISR_TRANS)
> ^
> /scratch/dja/linux-capi/drivers/misc/cxl/irq.c: In function ‘fail_psl_irq’:
> /scratch/dja/linux-capi/drivers/misc/cxl/irq.c:184:5: warning: suggest explicit braces to avoid ambiguous ‘else’ [-Wparentheses]
> if (irq_info->dsisr & CXL_PSL_DSISR_TRANS)
> ^
>
> They're annoying. Fix them by inserting the braces.
>
> Signed-off-by: Daniel Axtens <dja@axtens.net>
> ---
> drivers/misc/cxl/irq.c | 5 +++--
> drivers/misc/cxl/pci.c | 5 +++--
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/misc/cxl/irq.c b/drivers/misc/cxl/irq.c
> index 121ec48f3ab4..c11e583a15a9 100644
> --- a/drivers/misc/cxl/irq.c
> +++ b/drivers/misc/cxl/irq.c
> @@ -181,10 +181,11 @@ static irqreturn_t cxl_irq(int irq, void *data, struct cxl_irq_info *irq_info)
>
> static irqreturn_t fail_psl_irq(struct cxl_afu *afu, struct cxl_irq_info *irq_info)
> {
> - if (irq_info->dsisr & CXL_PSL_DSISR_TRANS)
> + if (irq_info->dsisr & CXL_PSL_DSISR_TRANS) {
> cxl_p2n_write(afu, CXL_PSL_TFC_An, CXL_PSL_TFC_An_AE);
> - else
> + } else {
> cxl_p2n_write(afu, CXL_PSL_TFC_An, CXL_PSL_TFC_An_A);
> + }
>
> return IRQ_HANDLED;
> }
Why does your GCC complain here at all? The code doesn't look ambiguous
to me... Which version of GCC are you using?
I just did a quick test compile here, and these warnings do not occur
for me.
Thomas
next prev parent reply other threads:[~2015-07-31 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 6:35 [PATCH] cxl: Fix ambiguous else warnings Daniel Axtens
2015-07-31 9:28 ` Thomas Huth [this message]
[not found] <1438324508-30341-1-git-send-email-dja__13473.5064967119$1438324749$gmane$org@axtens.net>
2015-07-31 9:16 ` Andreas Schwab
2015-08-03 0:36 ` Daniel Axtens
2015-08-03 0:43 ` Michael Ellerman
2015-08-03 0:47 ` Daniel Axtens
2015-08-03 1:37 ` Michael Ellerman
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=55BB3FB8.9010606@redhat.com \
--to=thuth@redhat.com \
--cc=dja@axtens.net \
--cc=imunsie@au.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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.