[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f34130034637278c9999cf6d430be558cb0c2318.camel@linux.ibm.com>
Date: Thu, 12 May 2022 16:56:42 +0200
From: Niklas Schnelle <schnelle@...ux.ibm.com>
To: Bjorn Helgaas <bhelgaas@...gle.com>,
Jan Kiszka <jan.kiszka@...mens.com>,
Matthew Rosato <mjrosato@...ux.ibm.com>,
Pierre Morel <pmorel@...ux.ibm.com>
Cc: linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
linux-s390@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH RESEND v5 1/4] PCI: Clean up pci_scan_slot()
On Thu, 2022-05-05 at 10:38 +0200, Niklas Schnelle wrote:
> While determining the next PCI function is factored out of
> pci_scan_slot() into next_fn() the former still handles the first
> function as a special case. This duplicates the code from the scan loop.
>
> Furthermore the non ARI branch of next_fn() is generally hard to
> understand and especially the check for multifunction devices is hidden
> in the handling of NULL devices for non-contiguous multifunction. It
> also signals that no further functions need to be scanned by returning
> 0 via wraparound and this is a valid function number.
>
> Improve upon this by transforming the conditions in next_fn() to be
> easier to understand.
>
> By changing next_fn() to return -ENODEV instead of 0 when there is no
> next function we can then handle the initial function inside the loop
> and deduplicate the shared handling. This also makes it more explicit
> that only function 0 must exist.
>
> No functional change is intended.
>
> Cc: Jan Kiszka <jan.kiszka@...mens.com>
> Signed-off-by: Niklas Schnelle <schnelle@...ux.ibm.com>
> ---
Friendly ping :-)
Powered by blists - more mailing lists