From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Takashi Sakamoto <o-takashi@sakamocchi•jp>
Cc: Li Zhijian <lizhijian@fujitsu•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the ieee1394 tree
Date: Fri, 2 Feb 2024 11:16:02 +1100 [thread overview]
Message-ID: <20240202111602.6f6e2c1a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
Hi all,
After merging the ieee1394 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/firewire/core-device.c: In function 'show_text_leaf':
drivers/firewire/core-device.c:369:48: error: 'bufsize' undeclared (first use in this function); did you mean 'ksize'?
369 | bufsize);
| ^~~~~~~
| ksize
Caused by commit
67a5a58c0443 ("firewire: Kill unnecessary buf check in device_attribute.show")
interacting with commit
47dc55181dcb ("firewire: core: search descriptor leaf just after vendor directory entry in root directory")
from Linus' tree (v6.8-rc2 - that the ieee1394 tree has just been rebased on
top of). I have dropped the ieee1394 tree for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-02 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 0:16 Stephen Rothwell [this message]
2024-02-02 1:04 ` linux-next: build failure after merge of the ieee1394 tree Takashi Sakamoto
-- strict thread matches above, loose matches on Subject: below --
2023-05-30 2:24 Stephen Rothwell
2023-05-30 10:44 ` Takashi Sakamoto
2010-07-27 1:48 Stephen Rothwell
2010-07-27 8:07 ` Stefan Richter
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=20240202111602.6f6e2c1a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lizhijian@fujitsu$(echo .)com \
--cc=o-takashi@sakamocchi$(echo .)jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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