Re: linux-next: manual merge of the bpf-next tree with the kbuild tree

["Alexei Starovoitov" <alexei.starovoitov@gmail.com>]

On Fri Oct 2, 2026 at 11:06 PM UTC, Nathan Chancellor wrote:
> Hi Mark,
>
> On Sat, Oct 03, 2026 at 12:42:58AM +0200, Mark Brown wrote:
>> Today's linux-next merge of the bpf-next tree got a conflict in:
>> 
>>   init/Kconfig
>> 
>> between commit:
>> 
>>   f85147b291e35 ("kbuild: move the toolchain checks into scripts/Kconfig.toolchain")
>> 
>> from the kbuild tree and commit:
>> 
>>   eb13a1ff271b0 ("random: vDSO: avoid call to memset() when zeroing reserved parameter")
>> 
>> from the bpf-next tree.
>
> For the record, this change is from Linus's tree, as it was merged in
>
>   ac7445c28e7a ("Merge tag 'random-7.3-rc6-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random")
>
> but presumably your stable base does not have that merge depending on
> whan you started -next so it comes in from the bpf-next merge of Linus's
> tree in
>
>   2b5440b31caf ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf 7.3-rc5")
>
> I just wanted to make sure the bpf folks didn't think they were on the
> hook for this conflict, it is only on me with the Kbuild tree now.

Thanks for the clarification.

The other reported conflict with pci-current is in the same category.
2b5440b31caf is what Linus's tree has. it's not bpf-next specific.