linux-kernel - Re: [PATCH V3] staging:vme_user:Fix the issue of return the wrong error code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 19 Dec 2023 16:18:32 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Piro Yang <piroyangg@...il.com>
Cc: linux-staging@...ts.linux.dev,
	Linux Outreachy <outreachy@...ts.linux.dev>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3] staging:vme_user:Fix the issue of return the wrong
 error code

On Tue, Dec 19, 2023 at 11:12:02PM +0800, Piro Yang wrote:
> Fix the issue of returning the -ENOSYS error code when an error occurs
> 
> The error code of -ENOSYS indicates Invalid system call number, but there is not system call error

Please wrap your changelog text at 72 columns, like your editor asked
you to.

And use '.' as these are real sentences, right?

And some ' ' in the subject line, like:
	staging: vme_user: Fix...

Usually writing the changelog and getting it correct is the hardest part
of getting a change accepted.

thanks,

greg k-h