From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
Jing Cai <jing.cai@mediatek.com>,
Chris Lu <chris.lu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>
Subject: Re: linux-next: Tree for Jun 30 (drivers/bluetooth/btmtk.c)
Date: Fri, 30 Jun 2023 17:09:38 -0700 [thread overview]
Message-ID: <2e729756-4468-9e3a-2664-9b1b4b4ca060@infradead.org> (raw)
In-Reply-To: <20230630131756.6dee658e@canb.auug.org.au>
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
prev parent reply other threads:[~2023-07-01 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 3:17 linux-next: Tree for Jun 30 Stephen Rothwell
2023-07-01 0:09 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e729756-4468-9e3a-2664-9b1b4b4ca060@infradead.org \
--to=rdunlap@infradead.org \
--cc=chris.lu@mediatek.com \
--cc=jing.cai@mediatek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).