From: domen@coderock.org
To: marcel@holtmann.org
Cc: bluez-devel@lists.sourceforge.net,
Victor Fusco <victor@cetuc.puc-rio.br>,
domen@coderock.org
Subject: [patch 2/3] hci_usb: fix sparse warnings (__nocast type)
Date: Thu, 07 Jul 2005 23:30:34 +0200 [thread overview]
Message-ID: <20050707213034.335385000@homer> (raw)
From: Victor Fusco <victor@cetuc.puc-rio.br>
Fix the sparse warning "implicit cast to nocast type"
File/Subsystem: drivers/bluetooth/hci_usb.c
Signed-off-by: Victor Fusco <victor@cetuc.puc-rio.br>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
hci_usb.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: quilt/drivers/bluetooth/hci_usb.c
===================================================================
--- quilt.orig/drivers/bluetooth/hci_usb.c
+++ quilt/drivers/bluetooth/hci_usb.c
@@ -126,7 +126,7 @@ static struct usb_device_id blacklist_id
{ } /* Terminating entry */
};
-static struct _urb *_urb_alloc(int isoc, int gfp)
+static struct _urb *_urb_alloc(int isoc, unsigned int __nocast gfp)
{
struct _urb *_urb = kmalloc(sizeof(struct _urb) +
sizeof(struct usb_iso_packet_descriptor) * isoc, gfp);
--
reply other threads:[~2005-07-07 21:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050707213034.335385000@homer \
--to=domen@coderock.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=victor@cetuc.puc-rio.br \
/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