[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2e729756-4468-9e3a-2664-9b1b4b4ca060@infradead.org>
Date: Fri, 30 Jun 2023 17:09:38 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
Jing Cai <jing.cai@...iatek.com>,
Chris Lu <chris.lu@...iatek.com>,
Sean Wang <sean.wang@...iatek.com>
Subject: Re: linux-next: Tree for Jun 30 (drivers/bluetooth/btmtk.c)
On 6/29/23 20:17, Stephen Rothwell wrote:
> Hi all,
>
> Please do *not* add any v6.6 related stuff to your linux-next included
> branches until after v6.5-rc1 has been released.
>
> This release is broken for 32 bit sparc builds.
>
> Changes since 20230629:
>
When CONFIG_DEV_COREDUMP is not set,
gcc 12.2.0 (crosstools from kernel.org) complains:
../drivers/bluetooth/btmtk.c: In function 'btmtk_process_coredump':
../drivers/bluetooth/btmtk.c:386:44: error: 'struct hci_dev' has no member named 'dump'
386 | schedule_delayed_work(&hdev->dump.dump_timeout,
|
I see this on arm64, ppc64, riscv32, i386, x86_64
PS: please add a MAINTAINERS entry for btmtk.c.
--
~Randy
Powered by blists - more mailing lists