Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1713223 > unrolled thread

Re: [PATCH] xen/pvcalls: use WARN_ON(1) instead of __WARN()

Started byBoris Ostrovsky <boris.ostrovsky@oracle.com>
First post2017-08-16 20:40 +0200
Last post2017-08-16 20:40 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] xen/pvcalls: use WARN_ON(1) instead of __WARN() Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2017-08-16 20:40 +0200

#1713223 — Re: [PATCH] xen/pvcalls: use WARN_ON(1) instead of __WARN()

FromBoris Ostrovsky <boris.ostrovsky@oracle.com>
Date2017-08-16 20:40 +0200
SubjectRe: [PATCH] xen/pvcalls: use WARN_ON(1) instead of __WARN()
Message-ID<ufbot-28f-5@gated-at.bofh.it>
On 07/21/2017 03:26 PM, Stefano Stabellini wrote:
> On Fri, 21 Jul 2017, Arnd Bergmann wrote:
>> __WARN() is an internal helper that is only available on
>> some architectures, but causes a build error e.g. on ARM64
>> in some configurations:
>>
>> drivers/xen/pvcalls-back.c: In function 'set_backend_state':
>> drivers/xen/pvcalls-back.c:1097:5: error: implicit declaration of function '__WARN' [-Werror=implicit-function-declaration]
>>
>> Unfortunately, there is no equivalent of BUG() that takes no
>> arguments, but WARN_ON(1) is commonly used in other drivers
>> and works on all configurations.
>>
>> Fixes: 7160378206b2 ("xen/pvcalls: xenbus state handling")
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
>

Applied to for-linus-4.14

-boris

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web