[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230720162756.08f2c66b@kernel.org>
Date: Thu, 20 Jul 2023 16:27:56 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "Von Dentz, Luiz" <luiz.von.dentz@...el.com>,
Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Networking <netdev@...r.kernel.org>,
"Alexander Mikhalitsyn" <alexander@...alicyn.com>,
Kuniyuki Iwashima <kuniyu@...zon.com>
Subject: Re: linux-next: build failure after merge of the bluetooth tree
On Fri, 21 Jul 2023 08:12:58 +1000 Stephen Rothwell wrote:
> > I kicked it off and forgot about it.
> > allmodconfig on 352ce39a8bbaec04 (next-20230719) builds just fine :S
>
> Of course it does, as commit
>
> 817efd3cad74 ("Bluetooth: hci_sock: Forward credentials to monitor")
>
> is reverted in linux-next. The question is "Does the bluetooth tree
> build?" or "Does the net-next tree build *if* you merge the bluetooth
> tree into it?"
Sorry for being slow, yes. I just did a test build with net-next and
bluetooth-next combined and allmodconfig is okay, so you should be good
to drop the revert. Fingers crossed.
Powered by blists - more mailing lists