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 1/3] bluetooth.h: fix sparse warnings (__nocast type)
Date: Thu, 07 Jul 2005 23:30:33 +0200 [thread overview]
Message-ID: <20050707213032.828120000@homer> (raw)
From: Victor Fusco <victor@cetuc.puc-rio.br>
Fix the sparse warning "implicit cast to nocast type"
File/Subsystem: include/net/bluetooth/bluetooth.h
Signed-off-by: Victor Fusco <victor@cetuc.puc-rio.br>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
bluetooth.h | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
Index: quilt/include/net/bluetooth/bluetooth.h
===================================================================
--- quilt.orig/include/net/bluetooth/bluetooth.h
+++ quilt/include/net/bluetooth/bluetooth.h
@@ -141,7 +141,8 @@ struct bt_skb_cb {
};
#define bt_cb(skb) ((struct bt_skb_cb *)(skb->cb))
-static inline struct sk_buff *bt_skb_alloc(unsigned int len, int how)
+static inline struct sk_buff *bt_skb_alloc(unsigned int len,
+ unsigned int __nocast how)
{
struct sk_buff *skb;
--
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=20050707213032.828120000@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