[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230720130003.6137c50f@canb.auug.org.au>
Date: Thu, 20 Jul 2023 13:00:03 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Jakub Kicinski <kuba@...nel.org>
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
Hi Jakub,
On Wed, 19 Jul 2023 18:24:39 -0700 Jakub Kicinski <kuba@...nel.org> wrote:
>
> Something weird. We did merge it, there was a sort-of-v2-called-v1:
>
> https://lore.kernel.org/all/20230627174314.67688-1-kuniyu@amazon.com/
>
> Merged as https://git.kernel.org/netdev/net-next/c/a9c49cc2f5b5
That is not the net-next tree in linux-next. I have always used
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git#main.
And the above commit is not in linux-next (yet?)
> Dunno how it's supposed to fix this particular issue, tho, on a closer
> look, as it still calls:
>
> scm_recv_unix() -> scm_pidfd_recv() -> pidfd_prepare()
Yeah, the bluetooth tree will need to change that after the above patch
is available to it.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists