From: Gustavo Padovan <gustavo@padovan.org>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 2/2] Bluetooth: rename parameter of alloc_skb
Date: Fri, 6 Apr 2012 20:15:48 -0300 [thread overview]
Message-ID: <1333754148-18796-2-git-send-email-gustavo@padovan.org> (raw)
In-Reply-To: <1333754148-18796-1-git-send-email-gustavo@padovan.org>
'flags' makes much more sense than 'nb'.
Signed-off-by: Gustavo Padovan <gustavo@padovan.org>
---
include/net/bluetooth/l2cap.h | 2 +-
net/bluetooth/l2cap_sock.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
index b74b3f9..193d3a1 100644
--- a/include/net/bluetooth/l2cap.h
+++ b/include/net/bluetooth/l2cap.h
@@ -522,7 +522,7 @@ struct l2cap_ops {
void (*close) (void *data);
void (*state_change) (void *data, int state);
struct sk_buff *(*alloc_skb) (struct l2cap_chan *chan,
- unsigned long len, int nb);
+ unsigned long len, int flags);
};
diff --git a/net/bluetooth/l2cap_sock.c b/net/bluetooth/l2cap_sock.c
index 1463b5d..5d68b51 100644
--- a/net/bluetooth/l2cap_sock.c
+++ b/net/bluetooth/l2cap_sock.c
@@ -927,12 +927,12 @@ static void l2cap_sock_state_change_cb(void *data, int state)
}
static struct sk_buff *l2cap_sock_alloc_skb_cb(struct l2cap_chan *chan,
- unsigned long len, int nb)
+ unsigned long len, int flags)
{
struct sk_buff *skb;
int err;
- skb = bt_skb_send_alloc(chan->sk, len, nb, &err);
+ skb = bt_skb_send_alloc(chan->sk, len, flags, &err);
if (!skb)
return (ERR_PTR(err));
--
1.7.7.6
next prev parent reply other threads:[~2012-04-06 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 23:15 [PATCH 1/2] Bluetooth: Remove err parameter from alloc_skb() Gustavo Padovan
2012-04-06 23:15 ` Gustavo Padovan [this message]
2012-04-07 11:47 ` [PATCH 2/2] Bluetooth: rename parameter of alloc_skb Marcel Holtmann
2012-04-07 11:44 ` [PATCH 1/2] Bluetooth: Remove err parameter from alloc_skb() Marcel Holtmann
2012-04-12 11:51 ` Johan Hedberg
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=1333754148-18796-2-git-send-email-gustavo@padovan.org \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).