Skip to contentSkip to conversation

linux-next: build failure in the final build

DISCUSSION Mark Brown 2 participants 4 messages Sep 25 – Sep 29 Linux-next tree

lore
Share & tools
lore

Mark Brown

author maintainer
#0 lore raw

Hi all,

In the final build today's linux-next build (i386 defconfig) failed like this:

/tmp/next/build/drivers/pci/probe.c: In function 'pci_class':
/tmp/next/build/drivers/pci/probe.c:1902:12: error: unused variable 'rev' [-Werror=unused-variable]
1902 | u8 rev;
| ^~~

Caused by commit

8a2a9fa37b814 (PCI/IOV: Read VF config values that need not match PF)

I have reverted that commit for today.

author maintainer
#1 lore raw
Quoted 10 lines · Mark Brown

Hi all,

In the final build today's linux-next build (i386 defconfig) failed like this:

/tmp/next/build/drivers/pci/probe.c: In function 'pci_class':
/tmp/next/build/drivers/pci/probe.c:1902:12: error: unused variable 'rev' [-Werror=unused-variable]
1902 | u8 rev;
| ^~~

Quoted 5 lines

Caused by commit

8a2a9fa37b814 (PCI/IOV: Read VF config values that need not match PF)

I have reverted that commit for today.

This issue is still present today.

#2 lore raw
Quoted 11 lines · Mark Brown
Quoted 10 lines · Mark Brown

Hi all,

In the final build today's linux-next build (i386 defconfig) failed like this:

/tmp/next/build/drivers/pci/probe.c: In function 'pci_class':
/tmp/next/build/drivers/pci/probe.c:1902:12: error: unused variable 'rev' [-Werror=unused-variable]
1902 | u8 rev;
| ^~~

Quoted 7 lines
Quoted 5 lines

Caused by commit

8a2a9fa37b814 (PCI/IOV: Read VF config values that need not match PF)

I have reverted that commit for today.

This issue is still present today.

Sorry, it should be fixed in the current pci/next
(81bebadfa0f7 ("Merge branch 'pci/misc'"))

author maintainer
#3 lore raw
Quoted 4 lines · Bjorn Helgaas
Quoted 1 line · Mark Brown
Quoted 1 line

Caused by commit

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

8a2a9fa37b814 (PCI/IOV: Read VF config values that need not match PF)

I have reverted that commit for today.

This issue is still present today.

Sorry, it should be fixed in the current pci/next
(81bebadfa0f7 ("Merge branch 'pci/misc'"))

Yes, it was gone today.