From: Dan Carpenter <dan.carpenter@oracle.com>
To: Martin Kaiser <martin@kaiser.cx>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] staging: rtl8188eu: remove dummy wext handlers
Date: Mon, 31 May 2021 09:02:24 +0300 [thread overview]
Message-ID: <20210531060223.GV1955@kadam> (raw)
In-Reply-To: <20210529121346.8422-2-martin@kaiser.cx>
On Sat, May 29, 2021 at 02:13:45PM +0200, Martin Kaiser wrote:
> Remove the wext handlers that link to an empty dummy function.
>
> Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> ---
> If no handler is installed for a wext ioctl, the wext core will return
> -ENOTSUPP to user space. The dummy function returned -1. It could be argued
> that this change breaks the user space ABI.
>
> However, it's rather unlikely that an application expects a particular wlan
> driver and chipset when it configures a wireless network. Checking for
> errno==1 explicitly will already be non-portable as most other drivers set
> errn==ENOTSUPP for non-existing ioctls.
>
The patch is good, but next time, just put all this commentary in the
commit message. It has to do with the impact of the patch on userspace
and it's helpful for the reviewers. Some reviewers won't need it, but
I try to target my commit messages at developers who aren't subsystem
experts. I also like that it shows you thought about it.
I recently saw someone claim that "anyone who can review these patches
will already know what the <SOMETHING> acronym stands for so that's why
I didn't explain." And I was like, "Oh wow... That's a harsh burn on
me!"
regards,
dan carpenter
next prev parent reply other threads:[~2021-05-31 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 12:13 [PATCH 1/3] staging: rtl8188eu: use IW_HANDLER to declare wext handlers Martin Kaiser
2021-05-29 12:13 ` [PATCH 2/3] staging: rtl8188eu: remove dummy " Martin Kaiser
2021-05-31 6:02 ` Dan Carpenter [this message]
2021-05-31 7:55 ` Martin Kaiser
2021-05-29 12:13 ` [PATCH 3/3] staging: rtl8188eu: remove dummy setfreq handler Martin Kaiser
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=20210531060223.GV1955@kadam \
--to=dan.carpenter@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
/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