diff options
| author | Niklas Schnelle <schnelle@linux.ibm.com> | 2022-06-28 16:30:57 +0200 |
|---|---|---|
| committer | Bjorn Helgaas <bhelgaas@google.com> | 2022-07-22 16:05:00 -0500 |
| commit | fbed59ed8781d7eecd7f45cde0188cf24eeb5c38 (patch) | |
| tree | d206169ce426ed2b26fe3274bf513ad1c5444559 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | c3df83e01a96ca569d261bcdffa2fb858b1012fa (diff) | |
PCI: Split out next_ari_fn() from next_fn()
In commit b1bd58e448f2 ("PCI: Consolidate "next-function" functions") the
next_fn() function subsumed the traditional and ARI-based next function
determination. This got rid of some needlessly complex function pointer
handling but also reduced the separation between these very different
methods of finding the next function. With the next_fn() cleaned up a bit
we can re-introduce this separation by moving out the ARI handling while
sticking with direct function calls.
Link: https://lore.kernel.org/r/20220628143100.3228092-3-schnelle@linux.ibm.com
Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Pierre Morel <pmorel@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions