From: Gertjan van Wingerde <gwingerde@gmail.com>
To: John Li <john.li.mediatek@gmail.com>
Cc: users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>,
John Li <chen-yang.li@mediatek.com>
Subject: Re: [PATCH] rt2x00:Add debug message for new chipset
Date: Wed, 08 Feb 2012 23:03:02 +0100 [thread overview]
Message-ID: <4F32F116.6040106@gmail.com> (raw)
In-Reply-To: <1328707524-11415-1-git-send-email-john.li.mediatek@gmail.com>
On 02/08/12 14:25, John Li wrote:
> From: John Li <chen-yang.li@mediatek.com>
>
> Signed-off-by: John Li <chen-yang.li@mediatek.com>
Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
> ---
> drivers/net/wireless/rt2x00/rt2800lib.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800lib.c b/drivers/net/wireless/rt2x00/rt2800lib.c
> index 22a1a8f..6bdf6d6 100644
> --- a/drivers/net/wireless/rt2x00/rt2800lib.c
> +++ b/drivers/net/wireless/rt2x00/rt2800lib.c
> @@ -3949,7 +3949,7 @@ int rt2800_init_eeprom(struct rt2x00_dev *rt2x00dev)
> case RT5390:
> break;
> default:
> - ERROR(rt2x00dev, "Invalid RT chipset detected.\n");
> + ERROR(rt2x00dev, "Invalid RT chipset 0x%04x detected.\n", rt2x00dev->chip.rt);
> return -ENODEV;
> }
>
> @@ -3968,7 +3968,7 @@ int rt2800_init_eeprom(struct rt2x00_dev *rt2x00dev)
> case RF5390:
> break;
> default:
> - ERROR(rt2x00dev, "Invalid RF chipset 0x%x detected.\n",
> + ERROR(rt2x00dev, "Invalid RF chipset 0x%04x detected.\n",
> rt2x00dev->chip.rf);
> return -ENODEV;
> }
--
---
Gertjan
next prev parent reply other threads:[~2012-02-08 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 13:25 [PATCH] rt2x00:Add debug message for new chipset John Li
2012-02-08 13:34 ` Helmut Schaa
2012-02-08 22:03 ` Gertjan van Wingerde [this message]
2012-02-12 15:30 ` Ivo Van Doorn
-- strict thread matches above, loose matches on Subject: below --
2012-02-08 6:09 John Li
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=4F32F116.6040106@gmail.com \
--to=gwingerde@gmail.com \
--cc=chen-yang.li@mediatek.com \
--cc=john.li.mediatek@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.com \
/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.