From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] qbman_portal.c: Update BUG_ON() call in qbman_swp_mc_submit
Date: Tue, 15 Dec 2015 08:52:19 +0800 [thread overview]
Message-ID: <566F6443.9090002@freescale.com> (raw)
In-Reply-To: <1448715883-14099-3-git-send-email-trini@konsulko.com>
On 11/28/2015 09:04 PM, Tom Rini wrote:
> With gcc-5.x we get a warning about the ambiguity of BUG_ON(!a != b) and
> becomes BUG_ON((!a) != b). In this case reading of the function leads to
> us wanting to rewrite this as BUG_ON(a != b).
>
> Cc: Prabhakar Kushwaha <prabhakar@freescale.com>
> Cc: Geoff Thorpe <Geoff.Thorpe@freescale.com>
> Cc: Haiying Wang <Haiying.Wang@freescale.com>
> Cc: Roy Pledge <Roy.Pledge@freescale.com>
> Cc: York Sun <yorksun@freescale.com>
> Signed-off-by: Tom Rini <trini@konsulko.com>
> ---
Applied to fsl-qoriq master. Awaiting upstream.
York
next prev parent reply other threads:[~2015-12-15 0:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 13:04 [U-Boot] [PATCH 1/4] eth-raw-os.c: Add cast to bind(2) call Tom Rini
2015-11-28 13:04 ` [U-Boot] [PATCH 2/4] fsl_*_serdes.c: Modify memset call in serdes_init Tom Rini
2015-11-29 9:34 ` Bin Meng
2015-12-15 0:51 ` York Sun
2015-11-28 13:04 ` [U-Boot] [PATCH 3/4] qbman_portal.c: Update BUG_ON() call in qbman_swp_mc_submit Tom Rini
2015-11-29 9:34 ` Bin Meng
2015-12-15 0:52 ` York Sun [this message]
2015-11-28 13:04 ` [U-Boot] [PATCH 4/4] arch/arm/cpu/arm920t/ep93xx/led.c: Mark inline functions as static inline Tom Rini
2015-11-29 9:34 ` Bin Meng
2015-12-06 22:07 ` [U-Boot] [U-Boot, " Tom Rini
2015-11-29 9:34 ` [U-Boot] [PATCH 1/4] eth-raw-os.c: Add cast to bind(2) call Bin Meng
2015-11-30 22:13 ` Joe Hershberger
2016-01-15 3:45 ` Bin Meng
2016-01-15 12:28 ` Tom Rini
2016-01-15 13:10 ` [U-Boot] [U-Boot,1/4] " Tom Rini
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=566F6443.9090002@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/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