diff options
| author |   Linus Torvalds <torvalds@linux-foundation.org> | 2022-12-12 20:06:35 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-12-12 20:06:35 -0800 |
| commit | ad0d9da164cb52e62637e427517b2060dc956a2d (patch) | |
| tree | 38883fca586da266024357ae86f296b5478b13a4 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | Merge tag 'fscrypt-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt (diff) | |
| parent | fsverity: simplify fsverity_get_digest() (diff) | |
| download | wireguard-linux-ad0d9da164cb52e62637e427517b2060dc956a2d.tar.xz wireguard-linux-ad0d9da164cb52e62637e427517b2060dc956a2d.zip | |
Merge tag 'fsverity-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt
Pull fsverity updates from Eric Biggers:
"The main change this cycle is to stop using the PG_error flag to track
verity failures, and instead just track failures at the bio level.
This follows a similar fscrypt change that went into 6.1, and it is a
step towards freeing up PG_error for other uses.
There's also one other small cleanup"
* tag 'fsverity-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt:
fsverity: simplify fsverity_get_digest()
fsverity: stop using PG_error to track error status
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions