[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20111220130231.b819d888246ce08a4660eaa4@canb.auug.org.au>
Date: Tue, 20 Dec 2011 13:02:31 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: David Miller <davem@...emloft.net>, <netdev@...r.kernel.org>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Mat Martineau <mathewm@...eaurora.org>,
"Gustavo F. Padovan" <padovan@...fusion.mobi>,
"John W. Linville" <linville@...driver.com>,
Andrei Emeltchenko <andrei.emeltchenko@...el.com>
Subject: linux-next: manual merge of the net-next tree with the wireless
tree
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/bluetooth/l2cap_core.c between commit 36e999a83a4a ("Bluetooth:
Prevent uninitialized data access in L2CAP configuration") from the
wireless tree and commit 66af7aaf9edf ("Bluetooth: EFS: parse L2CAP
config response") from the net-next tree.
Just context changes. I fixed it up (see below) and can carry the fix as
necessary.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
diff --cc net/bluetooth/l2cap_core.c
index 17b5b1c,014fdec..0000000
--- a/net/bluetooth/l2cap_core.c
+++ b/net/bluetooth/l2cap_core.c
@@@ -2152,7 -2372,8 +2372,8 @@@ static int l2cap_parse_conf_rsp(struct
void *ptr = req->data;
int type, olen;
unsigned long val;
- struct l2cap_conf_rfc rfc;
+ struct l2cap_conf_rfc rfc = { .mode = L2CAP_MODE_BASIC };
+ struct l2cap_conf_efs efs;
BT_DBG("chan %p, rsp %p, len %d, req %p", chan, rsp, len, data);
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists