From: Sasha Levin <sashal@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: torvalds@linux-foundation.org, kuba@kernel.org,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Networking for v6.13-rc1
Date: Thu, 28 Nov 2024 11:06:09 -0500 [thread overview]
Message-ID: <Z0iU8QcgrC7QBEOQ@sashalap> (raw)
In-Reply-To: <a4213a79-dd00-4d29-9215-97eb69f75f39@redhat.com>
On Thu, Nov 28, 2024 at 04:46:40PM +0100, Paolo Abeni wrote:
>On 11/28/24 15:48, Sasha Levin wrote:
>> On Thu, Nov 28, 2024 at 03:27:38PM +0100, Paolo Abeni wrote:
>>> ipmr: add debug check for mr table cleanup
>>
>> When merging this PR into linus-next, I've noticed it introduced build
>> errors:
>>
>> /builds/linux/net/ipv4/ipmr.c:320:13: error: function 'ipmr_can_free_table' is not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration]
>> 320 | static bool ipmr_can_free_table(struct net *net)
>> | ^~~~~~~~~~~~~~~~~~~
>> 1 error generated.
>>
>> The commit in question isn't in linux-next and seems to be broken.
>
>My fault, I'm sorry.
>
>I can't reproduce the issue here. Could you please share your kconfig
>and the compiler version? I'll try to address the issue and re-send the
>PR ASAP.
All the build info for one for the failures is available here:
https://qa-reports.linaro.org/lkft/sashal-linus-next/build/v6.11-25635-g6813e2326f1e/testrun/26111580/suite/build/test/clang-nightly-lkftconfig/details/
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-11-28 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 14:27 [GIT PULL] Networking for v6.13-rc1 Paolo Abeni
2024-11-28 14:48 ` Sasha Levin
2024-11-28 15:46 ` Paolo Abeni
2024-11-28 16:01 ` Paolo Abeni
2024-11-28 16:06 ` Sasha Levin [this message]
2024-11-28 19:19 ` pr-tracker-bot
2024-11-29 5:38 ` patchwork-bot+netdevbpf
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=Z0iU8QcgrC7QBEOQ@sashalap \
--to=sashal@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=torvalds@linux-foundation.org \
/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).