From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Mihai Donțu" <mdontu@bitdefender.com>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] console: const-ify the arguments for __warn() and __bug()
Date: Mon, 8 Dec 2014 10:28:41 +0000 [thread overview]
Message-ID: <54857D59.2050605@citrix.com> (raw)
In-Reply-To: <1417997962-23853-1-git-send-email-mdontu@bitdefender.com>
On 08/12/14 00:19, Mihai Donțu wrote:
> Both __warn() and __bug() take as first parameter the file name of the
> current compilation unit (__FILE__). Mark that parameter as constant to
> better reflect that.
>
> Signed-off-by: Mihai Donțu <mdontu@bitdefender.com>
This seems reasonable, but for 4.6 at this point.
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
In future, please CC the relevant maintainers (scrips/get_maintainer.pl
should help)
> ---
> xen/drivers/char/console.c | 4 ++--
> xen/include/xen/lib.h | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/xen/drivers/char/console.c b/xen/drivers/char/console.c
> index 2f03259..7807cf2 100644
> --- a/xen/drivers/char/console.c
> +++ b/xen/drivers/char/console.c
> @@ -1138,7 +1138,7 @@ void panic(const char *fmt, ...)
> machine_restart(5000);
> }
>
> -void __bug(char *file, int line)
> +void __bug(const char *file, int line)
> {
> console_start_sync();
> printk("Xen BUG at %s:%d\n", file, line);
> @@ -1146,7 +1146,7 @@ void __bug(char *file, int line)
> panic("Xen BUG at %s:%d", file, line);
> }
>
> -void __warn(char *file, int line)
> +void __warn(const char *file, int line)
> {
> printk("Xen WARN at %s:%d\n", file, line);
> dump_execution_state();
> diff --git a/xen/include/xen/lib.h b/xen/include/xen/lib.h
> index f11b49e..8f9cadb 100644
> --- a/xen/include/xen/lib.h
> +++ b/xen/include/xen/lib.h
> @@ -8,8 +8,8 @@
> #include <xen/string.h>
> #include <asm/bug.h>
>
> -void noreturn __bug(char *file, int line);
> -void __warn(char *file, int line);
> +void noreturn __bug(const char *file, int line);
> +void __warn(const char *file, int line);
>
> #define BUG_ON(p) do { if (unlikely(p)) BUG(); } while (0)
> #define WARN_ON(p) do { if (unlikely(p)) WARN(); } while (0)
> --
> 2.2.0
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-12-08 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 0:19 [PATCH] console: const-ify the arguments for __warn() and __bug() Mihai Donțu
2014-12-08 10:28 ` Andrew Cooper [this message]
2014-12-09 17:55 ` Mihai Donțu
-- strict thread matches above, loose matches on Subject: below --
2014-12-10 12:22 Mihai Donțu
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=54857D59.2050605@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=mdontu@bitdefender.com \
--cc=xen-devel@lists.xenproject.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.