linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: WARN_ON() is buggy for 32 bit systems
Date: Wed, 26 Jan 2022 16:49:48 +0300	[thread overview]
Message-ID: <20220126134948.GA1978@kadam> (raw)
In-Reply-To: <8bfa7bbe-7343-2d2f-d20b-d4789523c89c@csgroup.eu>

On Wed, Jan 26, 2022 at 12:21:49PM +0000, Christophe Leroy wrote:
> The code is enclosed in a #ifdef CONFIG_PPC64, it is not used for PPC32:
> 
> /arch/powerpc/include/asm/bug.h
>    99  #ifdef CONFIG_PPC64

Ah...

You know, life would be a lot easier for me personally if we added an
#ifndef __CHECKER__ as well...  I can't compile PowerPC code so I can't
test a patch like that.

regards,
dan carpenter


  reply	other threads:[~2022-01-26 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 11:56 WARN_ON() is buggy for 32 bit systems Dan Carpenter
2022-01-26 12:21 ` Christophe Leroy
2022-01-26 13:49   ` Dan Carpenter [this message]
2022-01-27 11:10     ` Michael Ellerman
2022-01-27 13:37       ` Dan Carpenter

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=20220126134948.GA1978@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linuxppc-dev@lists.ozlabs.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).