From: Larry Finger <Larry.Finger@lwfinger.net>
To: thomas@fjellstrom.ca
Cc: linux-wireless@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: wil6210 driver compilation failure
Date: Sat, 20 Jul 2013 16:12:10 -0500 [thread overview]
Message-ID: <51EAFD2A.6060909@lwfinger.net> (raw)
In-Reply-To: <1546638.YtIzlZyRv2@balsa>
[-- Attachment #1: Type: text/plain, Size: 229 bytes --]
On 07/20/2013 02:40 PM, Thomas Fjellstrom wrote:
>
> The warnings have gone away, and the first error, but the second one is still
> there.
Sorry, I missed the second one in your original message. Does this one fix it?
Larry
[-- Attachment #2: wil6210_compile --]
[-- Type: text/plain, Size: 882 bytes --]
Index: linux-2.6/drivers/net/wireless/ath/wil6210/debugfs.c
===================================================================
--- linux-2.6.orig/drivers/net/wireless/ath/wil6210/debugfs.c
+++ linux-2.6/drivers/net/wireless/ath/wil6210/debugfs.c
@@ -145,7 +145,7 @@ static void wil_print_ring(struct seq_fi
le16_to_cpu(hdr.type), hdr.flags);
if (len <= MAX_MBOXITEM_SIZE) {
int n = 0;
- unsigned char printbuf[16 * 3 + 2];
+ char printbuf[16 * 3 + 2];
unsigned char databuf[MAX_MBOXITEM_SIZE];
void __iomem *src = wmi_buffer(wil, d.addr) +
sizeof(struct wil6210_mbox_hdr);
@@ -416,7 +416,7 @@ static int wil_txdesc_debugfs_show(struc
seq_printf(s, " SKB = %p\n", skb);
if (skb) {
- unsigned char printbuf[16 * 3 + 2];
+ char printbuf[16 * 3 + 2];
int i = 0;
int len = le16_to_cpu(d->dma.length);
void *p = skb->data;
next prev parent reply other threads:[~2013-07-20 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 18:37 wil6210 driver compilation failure Thomas Fjellstrom
2013-07-20 19:14 ` Larry Finger
2013-07-20 19:40 ` Thomas Fjellstrom
2013-07-20 21:12 ` Larry Finger [this message]
2013-07-20 22:48 ` Thomas Fjellstrom
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=51EAFD2A.6060909@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@fjellstrom.ca \
/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.