From: Greg KH <gregkh@linuxfoundation.org>
To: Piro Yang <piroyangg@gmail.com>
Cc: linux-staging@lists.linux.dev,
Linux Outreachy <outreachy@lists.linux.dev>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] staging:vme_user:Fix the issue of return the wrong error code
Date: Tue, 19 Dec 2023 16:18:32 +0100 [thread overview]
Message-ID: <2023121920-winter-devourer-4f0b@gregkh> (raw)
In-Reply-To: <20231219151202.50368-1-piroyangg@gmail.com>
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
prev parent reply other threads:[~2023-12-19 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 15:12 [PATCH V3] staging:vme_user:Fix the issue of return the wrong error code Piro Yang
2023-12-19 15:18 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023121920-winter-devourer-4f0b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=piroyangg@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox