Well checkpatch.pl still complained:

ERROR: trailing whitespace #157: FILE: Documentation/driver-api/dma-buf.rst:80: +  If llseek on dma-buf FDs isn't supported the kernel will report -ESPIPE for all^M$

That actually looks like you used a Windows line ending.

I fixed it up and pushed the patch, but please take a bit more care next time.

Thanks, Christian.

Am 17.04.24 um 06:59 schrieb Baruch Siach:

Use 'supported' instead of 'support'. 'support' makes no sense in this context.

Signed-off-by: Baruch Siach baruch@tkos.co.il

v2: Add commit log message (Christian König)

Documentation/driver-api/dma-buf.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/driver-api/dma-buf.rst b/Documentation/driver-api/dma-buf.rst index 0c153d79ccc4..29abf1eebf9f 100644 --- a/Documentation/driver-api/dma-buf.rst +++ b/Documentation/driver-api/dma-buf.rst @@ -77,7 +77,7 @@ consider though: the usual size discover pattern size = SEEK_END(0); SEEK_SET(0). Every other llseek operation will report -EINVAL.

• If llseek on dma-buf FDs isn't support the kernel will report -ESPIPE for all

• If llseek on dma-buf FDs isn't supported the kernel will report -ESPIPE for all cases. Userspace can use this to detect support for discovering the dma-buf size using llseek.