From: Ivo van Doorn <ivdoorn@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 6/8] rfkill: use the new WARN()
Date: Sun, 3 Aug 2008 10:10:13 +0200 [thread overview]
Message-ID: <200808031010.14048.IvDoorn@gmail.com> (raw)
In-Reply-To: <1217700664-20792-7-git-send-email-hmh@hmh.eng.br>
On Saturday 02 August 2008, Henrique de Moraes Holschuh wrote:
> Switch use of WARN_ON(1) to the new WARN() macro. Do this on a separate
> patch to make rfkill backports easier on trees like wireless-compat.
I rather see it merged into the other patch, backporting shouldn't really
be kept in mind for development for the next kernel.
The WARN() macro can easily be backported, and it doesn't make a real difference
if this patch is provided seperately or merged with the pevious one.
Both patches will end up in the same backport package anyway ;)
> Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Cc: Ivo van Doorn <IvDoorn@gmail.com>
> ---
> net/rfkill/rfkill.c | 28 +++++++++++++++++++++-------
> 1 files changed, 21 insertions(+), 7 deletions(-)
>
> diff --git a/net/rfkill/rfkill.c b/net/rfkill/rfkill.c
> index d5f95cb..88368c4 100644
> --- a/net/rfkill/rfkill.c
> +++ b/net/rfkill/rfkill.c
> @@ -204,7 +204,9 @@ static int rfkill_toggle_radio(struct rfkill *rfkill,
> * RFKILL_STATE_HARD_BLOCKED */
> break;
> default:
> - WARN_ON(1);
> + WARN(1, KERN_WARNING
> + "rfkill: illegal state %d passed as parameter "
> + "to rfkill_toggle_radio\n", state);
> return -EINVAL;
> }
>
> @@ -240,7 +242,9 @@ static void __rfkill_switch_all(const enum rfkill_type type,
> struct rfkill *rfkill;
>
> if (unlikely(state >= RFKILL_STATE_MAX || type >= RFKILL_TYPE_MAX)) {
> - WARN_ON(1);
> + WARN(1, KERN_WARNING
> + "rfkill: illegal state %d or type %d passed as "
> + "parameter to __rfkill_switch_all\n", state, type);
> return;
> }
>
> @@ -341,7 +345,9 @@ int rfkill_force_state(struct rfkill *rfkill, enum rfkill_state state)
>
> BUG_ON(!rfkill);
> if (unlikely(state >= RFKILL_STATE_MAX)) {
> - WARN_ON(1);
> + WARN(1, KERN_WARNING
> + "rfkill: illegal state %d passed as parameter "
> + "to rfkill_force_state\n", state);
> return -EINVAL;
> }
>
> @@ -600,7 +606,9 @@ static int rfkill_check_duplicity(const struct rfkill *rfkill)
>
> list_for_each_entry(p, &rfkill_list, node) {
> if (p == rfkill) {
> - WARN_ON(1);
> + WARN(1, KERN_WARNING
> + "rfkill: illegal attempt to register "
> + "an already registered rfkill struct\n");
> return -EEXIST;
> }
> set_bit(p->type, seen);
> @@ -671,7 +679,9 @@ struct rfkill * __must_check rfkill_allocate(struct device *parent,
> struct device *dev;
>
> if (type >= RFKILL_TYPE_MAX) {
> - WARN_ON(1);
> + WARN(1, KERN_WARNING
> + "rfkill: illegal type %d passed as parameter "
> + "to rfkill_allocate\n", type);
> return NULL;
> }
>
> @@ -751,7 +761,9 @@ int __must_check rfkill_register(struct rfkill *rfkill)
> !rfkill->toggle_radio ||
> rfkill->type >= RFKILL_TYPE_MAX ||
> rfkill->state >= RFKILL_STATE_MAX)) {
> - WARN_ON(1);
> + WARN(1, KERN_WARNING
> + "rfkill: attempt to register a "
> + "badly initialized rfkill struct\n");
> return -EINVAL;
> }
>
> @@ -827,7 +839,9 @@ int rfkill_set_default(enum rfkill_type type, enum rfkill_state state)
> if (type >= RFKILL_TYPE_MAX ||
> (state != RFKILL_STATE_SOFT_BLOCKED &&
> state != RFKILL_STATE_UNBLOCKED)) {
> - WARN_ON(1);
> + WARN(1, KERN_WARNING
> + "rfkill: illegal state %d or type %d passed as "
> + "parameter to rfkill_set_default\n", state, type);
> return -EINVAL;
> }
>
next prev parent reply other threads:[~2008-08-03 7:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 18:10 [GIT PATCH] rfkill changes for 2.6.28, set 1 Henrique de Moraes Holschuh
2008-08-02 18:10 ` [PATCH 1/8] rfkill: detect bogus double-registering (v2) Henrique de Moraes Holschuh
2008-08-03 8:04 ` Ivo van Doorn
2008-08-02 18:10 ` [PATCH 2/8] rfkill: add default global states (v2) Henrique de Moraes Holschuh
2008-08-03 8:05 ` Ivo van Doorn
2008-08-02 18:10 ` [PATCH 3/8] rfkill: add __must_check annotations Henrique de Moraes Holschuh
2008-08-03 8:05 ` Ivo van Doorn
2008-08-02 18:11 ` [PATCH 4/8] rfkill: introduce RFKILL_STATE_MAX Henrique de Moraes Holschuh
2008-08-03 8:06 ` Ivo van Doorn
2008-08-02 18:11 ` [PATCH 5/8] rfkill: add WARN_ON and BUG_ON paranoia Henrique de Moraes Holschuh
2008-08-03 8:07 ` Ivo van Doorn
2008-08-03 8:57 ` Johannes Berg
2008-08-03 10:07 ` Ivo van Doorn
2008-08-03 13:28 ` Henrique de Moraes Holschuh
2008-08-03 13:53 ` Ivo van Doorn
2008-08-03 13:36 ` Henrique de Moraes Holschuh
2008-08-03 13:21 ` Henrique de Moraes Holschuh
2008-08-03 13:50 ` Ivo van Doorn
2008-08-03 18:12 ` Johannes Berg
2008-08-02 18:11 ` [PATCH 6/8] rfkill: use the new WARN() Henrique de Moraes Holschuh
2008-08-03 8:10 ` Ivo van Doorn [this message]
2008-08-03 13:32 ` Henrique de Moraes Holschuh
2008-08-02 18:11 ` [PATCH 7/8] rfkill: rename rfkill_mutex to rfkill_global_mutex Henrique de Moraes Holschuh
2008-08-02 18:11 ` [PATCH 8/8] rfkill: add support for wake-on-wireless-packet Henrique de Moraes Holschuh
2008-08-02 19:02 ` Johannes Berg
2008-08-02 19:27 ` Henrique de Moraes Holschuh
2008-08-02 21:21 ` Tomas Winkler
2008-08-03 3:55 ` Henrique de Moraes Holschuh
2008-08-03 6:03 ` Tomas Winkler
2008-08-03 13:52 ` Henrique de Moraes Holschuh
2008-08-03 15:49 ` Tomas Winkler
2008-08-03 18:25 ` Henrique de Moraes Holschuh
2008-08-03 22:36 ` Tomas Winkler
2008-08-04 2:52 ` Henrique de Moraes Holschuh
2008-08-03 8:12 ` Ivo van Doorn
2008-08-03 8:07 ` Tomas Winkler
2008-08-03 13:44 ` Henrique de Moraes Holschuh
2008-08-03 14:12 ` Tomas Winkler
2008-08-04 15:42 ` Dan Williams
2008-08-04 22:30 ` Henrique de Moraes Holschuh
2008-08-04 22:56 ` Dan Williams
2008-08-04 23:35 ` Henrique de Moraes Holschuh
2008-08-05 9:12 ` Johannes Berg
2008-08-05 12:48 ` Henrique de Moraes Holschuh
2008-08-05 12:50 ` Johannes Berg
2008-08-05 12:59 ` Johannes Berg
2008-08-05 20:44 ` Henrique de Moraes Holschuh
2008-08-05 20:54 ` Johannes Berg
2008-08-05 13:03 ` Dan Williams
2008-08-05 14:00 ` John W. Linville
2008-08-05 18:37 ` Ivo van Doorn
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=200808031010.14048.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=linux-wireless@vger.kernel.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).