From: "Maksim (Max) Krasnyanskiy" <maxk@qualcomm.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5 patch] fix the compilation of drivers/bluetooth/bt3c_cs.c
Date: Mon, 21 Oct 2002 13:32:34 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20021021133129.0595cc40@mail1.qualcomm.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0210191134170.28761-100000@mimas.fachschafte n.tu-muenchen.de>
Yep. I got this from Marcel Holtmann already.
Thanks anyway.
Max
At 11:37 AM 10/19/2002 +0200, Adrian Bunk wrote:
>Hi Maksim,
>
>your bluetooth patches in 2.5.44 caused the following compile error in
>drivers/bluetooth/bt3c_cs.c that is fixed by the patch below:
>
><-- snip -->
>
>...
> gcc -Wp,-MD,drivers/bluetooth/.bt3c_cs.o.d -D__KERNEL__ -Iinclude -Wall
>-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
>-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6
>-Iarch/i386/mach-generic -nostdinc -iwithprefix include -DKBUILD_BASENAME=bt3c_cs -c -o
>drivers/bluetooth/bt3c_cs.o drivers/bluetooth/bt3c_cs.c
>drivers/bluetooth/bt3c_cs.c: In function `bt3c_receive':
>drivers/bluetooth/bt3c_cs.c:321: `hci_event_hdr' undeclared (first use in
>this function)
>drivers/bluetooth/bt3c_cs.c:321: (Each undeclared identifier is reported
>only once
>drivers/bluetooth/bt3c_cs.c:321: for each function it appears in.)
>drivers/bluetooth/bt3c_cs.c:321: `eh' undeclared (first use in this
>function)
>drivers/bluetooth/bt3c_cs.c:321: warning: statement with no effect
>drivers/bluetooth/bt3c_cs.c:322: `hci_acl_hdr' undeclared (first use in
>this function)
>drivers/bluetooth/bt3c_cs.c:322: `ah' undeclared (first use in this
>function)
>drivers/bluetooth/bt3c_cs.c:322: warning: statement with no effect
>drivers/bluetooth/bt3c_cs.c:323: `hci_sco_hdr' undeclared (first use in
>this function)
>drivers/bluetooth/bt3c_cs.c:323: `sh' undeclared (first use in this
>function)
>drivers/bluetooth/bt3c_cs.c:323: warning: statement with no effect
>drivers/bluetooth/bt3c_cs.c:328: parse error before `)'
>drivers/bluetooth/bt3c_cs.c:334: parse error before `)'
>drivers/bluetooth/bt3c_cs.c:341: parse error before `)'
>drivers/bluetooth/bt3c_cs.c:320: warning: `dlen' might be used
>uninitialized in
>this function
>make[2]: *** [drivers/bluetooth/bt3c_cs.o] Error 1
>
><-- snip -->
>
>
>cu
>Adrian
>
>--- linux-2.5.44-full/drivers/bluetooth/bt3c_cs.c.old 2002-10-19 11:23:35.000000000 +0200
>+++ linux-2.5.44-full/drivers/bluetooth/bt3c_cs.c 2002-10-19 11:24:44.000000000 +0200
>@@ -318,27 +318,27 @@
> if (info->rx_count == 0) {
>
> int dlen;
>- hci_event_hdr *eh;
>- hci_acl_hdr *ah;
>- hci_sco_hdr *sh;
>+ struct hci_event_hdr *eh;
>+ struct hci_acl_hdr *ah;
>+ struct hci_sco_hdr *sh;
>
> switch (info->rx_state) {
>
> case RECV_WAIT_EVENT_HEADER:
>- eh = (hci_event_hdr *)(info->rx_skb->data);
>+ eh = (struct hci_event_hdr *)(info->rx_skb->data);
> info->rx_state = RECV_WAIT_DATA;
> info->rx_count = eh->plen;
> break;
>
> case RECV_WAIT_ACL_HEADER:
>- ah = (hci_acl_hdr *)(info->rx_skb->data);
>+ ah = (struct hci_acl_hdr *)(info->rx_skb->data);
> dlen = __le16_to_cpu(ah->dlen);
> info->rx_state = RECV_WAIT_DATA;
> info->rx_count = dlen;
> break;
>
> case RECV_WAIT_SCO_HEADER:
>- sh = (hci_sco_hdr *)(info->rx_skb->data);
>+ sh = (struct hci_sco_hdr *)(info->rx_skb->data);
> info->rx_state = RECV_WAIT_DATA;
> info->rx_count = sh->dlen;
> break;
next parent reply other threads:[~2002-10-21 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.NEB.4.44.0210191134170.28761-100000@mimas.fachschafte n.tu-muenchen.de>
2002-10-21 20:32 ` Maksim (Max) Krasnyanskiy [this message]
2002-10-19 9:37 Adrian Bunk
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=5.1.0.14.2.20021021133129.0595cc40@mail1.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®