pci: Fix dependency on ACPICA for non-ACPI builds

[obiwac]

Summary

Commit 84bbfc32a3f4 introduced a dependency on ACPICA for non-ACPI builds. This fixes that.

While here, print "D3hot" for D3hot in ACPI code instead of just "D3", as it was unclear whether that referred to D3hot or D3cold and was inconsistent with the PCI_POWERSTATE_D3 and ACPI_D_STATE_D3 defines.

Sponsored by: The FreeBSD Foundation.
Fixes: 84bbfc32a3f4 ("acpi_powerres: D3cold support")

[jrtc27]

sys/dev/pci/pcivar.h

526

PCI_POWERSTATE_D3 is PCI_POWERSTATE_D3_COLD but we print PCI_POWERSTATE_D3_HOT as "D3"?

[obiwac]

Print D3hot instead of just D3.

[obiwac]

sys/dev/pci/pcivar.h

526

Yeah I believe we should print D3hot. Let me just double-check the ACPICA change because this was a while ago for me.

If this is wrong then I need to change this in acpi_d_state_to_str too.

[des]

A better commit message would be:

pci: Fix dependency on ACPI

While here, print "D3hot" for D3hot in ACPI code instead of just "D3".

Fixes:		84bbfc32a3f47bd2e32741247afe516cbeff7789

[obiwac]

thanks, will use your commit message on commit :)

I'm guessing I can shorten the hash and add the commit title in "Fixes:"?

[des]

In D51823#1184154, @obiwac wrote:

I'm guessing I can shorten the hash and add the commit title in "Fixes:"?

I usually just use the first twelve characters of the hash and no commit title. If you include the title, it has to be ("in parentheses and double quotes").

[jrtc27]

Correctly-formatted commit message would be:

Commit 84bbfc32a3f4 ("acpi_powerres: D3cold support") introduced a
dependency on ACPICA for non-ACPI builds. This fixes that.

Uses the opportunity to print "D3hot" for D3hot in ACPI code instead of
just "D3".

Fixes:		84bbfc32a3f4 ("acpi_powerres: D3cold support")
Sponsored by:	The FreeBSD Foundation

But also this doesn't fully explain *why* we should print D3hot rather than D3, namely that it was inconsistent in whether D3 meant hot or cold when unqualified. Please explain that in your own words, as the commit message should be the "why", not just the "what" (because, after all, the "what" is already there in the form of the diff).

[jrtc27]

In D51823#1184158, @des wrote:

In D51823#1184154, @obiwac wrote:

I'm guessing I can shorten the hash and add the commit title in "Fixes:"?

I usually just use the first twelve characters of the hash and no commit title. If you include the title, it has to be ("in parentheses and double quotes").

Please always use the subject for a given hash at least once in the commit message. It's fine to elide in the body if Fixes: mentions it, for example, but not including the subject at all can be a problem for short hash collisions (maybe 12 is fine, but maybe it isn't), and also makes it easier to cross-reference things if we ever have to change VCS again (c.f. how annoying it is to have to find the corresponding git commit for an SVN revision mentioned in a commit message). It's also just more human-friendly; I don't remember commit hashes, but I might remember a commit from its subject.

[obiwac]

Thanks for your comments Jessica. Is the description as it stands now to your liking? I will wrap at 72 columns and format the metadata correctly on commit.

[jrtc27]

That looks a lot better now, thanks.

[ngie]

Please commit this change: it not being fixed in resulting in deterministic kernel build failures on powerpc*, risc64, etc.
CC: @cperciva