summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2024-05-29 11:08:05 +0100
committerMark Brown <broonie@kernel.org>2024-05-29 11:08:05 +0100
commitb0d8c563f0fb1dba8b10edc2553783f6ad058303 (patch)
treedbf13cc6cef1a2d77c8c3a341da19095957a4db3 /tools/perf/scripts/python/export-to-postgresql.py
parentab0b5a99d371da201e65640a94d68c5322d9d6bd (diff)
parent41b86b1455079600fa2b13e59f7c6f256d1d3131 (diff)
spi: differentiate between unsupported and invalid
Merge series from Miquel Raynal <miquel.raynal@bootlin.com>: I am working on spi-nand continuous read support, which lead me to check what spi controllers were capable of. >From a caller (and reviewer) point of view, distinguishing between error cases has been proven useful, especially between two conditions: - the request is totally unsupported and will never work - the request is typically out of range somehow but a subsequent call with corrected parameters might work So while I was statically reading the various drivers, I attempted to clarify these situations and thought it might be nice to have this upstream as well. As ENOTSUPP is not a SUSV4 code and previous series have already been merged to reduce its use, I also converted these few cases to EOPNOTSUP instead, but if anybody doesn't like these changes, it can be dropped.
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions