BPF CI and stable backports (was Re: [PATCH stable 6.6 2/2] selftests/bpf: Add a test to verify previous stacksafe() fix)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Fri, Aug 23, 2024 at 01:53:48AM GMT, bot+bpf-ci@xxxxxxxxxx wrote:
[...]
> CI has tested the following submission:
> Status:     CONFLICT
> Name:       [stable,6.6,2/2] selftests/bpf: Add a test to verify previous stacksafe() fix
> Patchwork:  https://patchwork.kernel.org/project/netdevbpf/list/?series=882411&state=*
> PR:         https://github.com/kernel-patches/bpf/pull/7584
> 
> Please rebase your submission onto the most recent upstream change and resubmit
> the patch to get it tested again.

It seems the BPF CI picks up stable patches and tries to apply it on top
of bpf-next, which fails to due conflict. Could a filter be added to CI
so these are ignored instead? (Or have BPF CI apply and test against
stable/linux-*, but that seems too much to ask)

OTOH if maintainers and reviewers prefers stable backport not to be sent
to the BPF mailing list, I will drop the CC to BPF mailing list in the
future.

Thanks,
Shung-Hsi

[...]




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux