linux-kernel - linux-next: build failure after merge of the bluetooth tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120222122109.7aef5c672df3bab843214606@canb.auug.org.au>
Date:	Wed, 22 Feb 2012 12:21:09 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	"Gustavo F. Padovan" <padovan@...fusion.mobi>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	"H. J. Lu" <hjl.tools@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	Marcel Holtmann <marcel@...tmann.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: linux-next: build failure after merge of the bluetooth tree

Hi Gustavo,

After merging the bluetooth tree, today's linux-next build
(x86_64_allmodconfig) failed like this:

net/bluetooth/hci_sock.c: In function 'hci_sock_cmsg':
net/bluetooth/hci_sock.c:738:8: error: 'COMPAT_USE_64BIT_TIME' undeclared (first use in this function)

Caused by commit aebb77ca6ad1 ("compat: Use COMPAT_USE_64BIT_TIME in the
Bluetooth subsystem").  That symbol doesn't exist anywhere in linux-next ...

I have used the bluetooth from next-20120221 for today.

P.S. that commit is supposedly authored by H. J. Lu but does not contain
a Signed-off-by from him.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped