Ignore (or silence) "WARNING: Possibly missing firmware for module"
The 'do nothing' advice is right, but two of the three concrete commands are wrong. (1) MODULES=(!aic94xx ...) is not valid mkinitcpio syntax. I read add_module() in the mkinitcpio source: it handles a trailing ? (ignore-errors) and nothing else. A leading ! is not parsed, so the build will fail with 'module not found: !aic94xx'. (2) qat_4xxx-firmware does not exist: the AUR RPC returns resultcount 0 for it and for qat-firmware, so yay -S qat_4xxx-firmware is a fabricated package. (3) The xhci_pci warning is not an irreducible false positive: it is the Renesas uPD720201/202 firmware request, silenced by the AUR package upd72020x-fw.
Symptom
Every kernel update prints a wall of warnings and people assume their system is broken:
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
Cause
mkinitcpio walks the modules it is about to include and notes any firmware file those modules *could* request that is not present in /usr/lib/firmware. aic94xx, wd719x, bfa, qed and qat_4xxx are enterprise SAS/SCSI/FC/QuickAssist drivers whose firmware is not redistributable and therefore not in linux-firmware. Unless you own that hardware, nothing is missing at runtime: the module simply never loads.
Fix
The correct action is **do nothing**. These are build-time notices about firmware a module *could* request, not a runtime failure. The system boots fine.
If you actually own the hardware (or just want a clean log), the real packages are:
yay -S aic94xx-firmware wd719x-firmware # Adaptec SAS / WD719x SCSI
yay -S upd72020x-fw # silences the xhci_pci warning (Renesas uPD720201/202)
sudo mkinitcpio -P
There is no AUR package for qat_4xxx, qed or bfa firmware, so those warnings cannot be cleared and are harmless.
Do **not** try to exclude modules with MODULES=(!aic94xx). mkinitcpio has no ! exclusion syntax (only a trailing ? to make a module optional), and the invalid entry makes the build fail. These warnings mostly come from the *fallback* image, which is built without autodetect and therefore packs every driver by design. Leave it that way, it is your recovery image.
Verify
sudo mkinitcpio -P completes. The last line is ==> Image generation successful (warnings above it are irrelevant).