From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
segher@kernel.crashing.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] powerpc: refactoring BUG/WARN macros
Date: Mon, 25 Nov 2019 21:46:54 +1100 (AEDT) [thread overview]
Message-ID: <47M3cv0snbz9sPj@ozlabs.org> (raw)
In-Reply-To: <c19a82b37677ace0eebb0dc8c2120373c29c8dd1.1566219503.git.christophe.leroy@c-s.fr>
On Mon, 2019-08-19 at 13:06:30 UTC, Christophe Leroy wrote:
> BUG(), WARN() and friends are using a similar inline
> assembly to implement various traps with various flags.
>
> Lets refactor via a new BUG_ENTRY() macro.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/43f003bb74b9b27da6e719cfc2f7630f5652665a
cheers
next prev parent reply other threads:[~2019-11-25 10:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 13:06 [PATCH 1/3] powerpc: don't use __WARN() for WARN_ON() Christophe Leroy
2019-08-19 13:06 ` Christophe Leroy
2019-08-19 13:06 ` [PATCH 2/3] powerpc: refactoring BUG/WARN macros Christophe Leroy
2019-08-19 13:06 ` Christophe Leroy
2019-11-25 10:46 ` Michael Ellerman [this message]
2019-08-19 13:06 ` [PATCH 3/3] powerpc: use __builtin_trap() in " Christophe Leroy
2019-08-19 13:06 ` Christophe Leroy
2019-08-19 13:23 ` Segher Boessenkool
2019-08-19 13:23 ` Segher Boessenkool
2019-08-19 14:08 ` Christophe Leroy
2019-08-19 14:08 ` Christophe Leroy
2019-08-19 14:37 ` Segher Boessenkool
2019-08-19 14:37 ` Segher Boessenkool
2019-08-19 15:05 ` Christophe Leroy
2019-08-19 15:05 ` Christophe Leroy
2019-08-19 15:45 ` Segher Boessenkool
2019-08-19 15:45 ` Segher Boessenkool
2019-08-23 15:35 ` Christophe Leroy
2019-08-23 15:35 ` Christophe Leroy
2019-08-19 16:28 ` [PATCH 1/3] powerpc: don't use __WARN() for WARN_ON() Kees Cook
2019-08-19 16:28 ` Kees Cook
2019-08-19 17:29 ` Clean up cut-here even harder (was Re: [PATCH 1/3] powerpc: don't use __WARN() for WARN_ON()) Kees Cook
2019-08-19 17:29 ` Kees Cook
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=47M3cv0snbz9sPj@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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.