From: Pavel Skripkin <paskripkin@gmail.com>
To: Phillip Potter <phil@philpotter.co.uk>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Greg KH <gregkh@linuxfoundation.org>,
Michael Straube <straube.linux@gmail.com>,
"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: r8188eu: make rtw_deinit_intf_priv return void
Date: Tue, 24 Aug 2021 00:29:16 +0300 [thread overview]
Message-ID: <262ccda0-0aed-26e9-0585-e5376db86596@gmail.com> (raw)
In-Reply-To: <CAA=Fs0mW_4aVNYuLkZMS9ov0CPNKfPB7C=FS2z67Ui+hEvtaRA@mail.gmail.com>
On 8/24/21 12:20 AM, Phillip Potter wrote:
> On Mon, 23 Aug 2021 at 19:41, Pavel Skripkin <paskripkin@gmail.com> wrote:
>>
>> rtw_deinit_intf_priv() always return success, so there is no need in
>> return value
>>
>> Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
>> ---
>> drivers/staging/r8188eu/os_dep/usb_intf.c | 5 +----
>> 1 file changed, 1 insertion(+), 4 deletions(-)
>>
>> diff --git a/drivers/staging/r8188eu/os_dep/usb_intf.c b/drivers/staging/r8188eu/os_dep/usb_intf.c
>> index e002070f7fba..37694aa96d13 100644
>> --- a/drivers/staging/r8188eu/os_dep/usb_intf.c
>> +++ b/drivers/staging/r8188eu/os_dep/usb_intf.c
>> @@ -129,13 +129,10 @@ static u8 rtw_init_intf_priv(struct dvobj_priv *dvobj)
>> return rst;
>> }
>>
>> -static u8 rtw_deinit_intf_priv(struct dvobj_priv *dvobj)
>> +static void rtw_deinit_intf_priv(struct dvobj_priv *dvobj)
>> {
>> - u8 rst = _SUCCESS;
>> -
>> kfree(dvobj->usb_alloc_vendor_req_buf);
>> _rtw_mutex_free(&dvobj->usb_vendor_req_mutex);
>> - return rst;
>> }
>>
>> static struct dvobj_priv *usb_dvobj_init(struct usb_interface *usb_intf)
>> --
>> 2.32.0
>>
>
> Dear Pavel,
>
> Looks good - going to test your RFC series now btw.
>
Thank you, Phillip!
Testing this RFC is very important. If it's all ok with it, I am going
to add proper error handling all across the driver code, based on read()
errors :)
Btw, we also can add error handling for write() operations, but I think
it's not _very_ important, since driver won't misbehave in case of write
failures
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2021-08-23 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 18:40 [PATCH] staging: r8188eu: make rtw_deinit_intf_priv return void Pavel Skripkin
2021-08-23 19:30 ` Martin Kaiser
2021-08-23 19:34 ` Michael Straube
2021-08-23 21:20 ` Phillip Potter
2021-08-23 21:29 ` Pavel Skripkin [this message]
2021-08-23 22:23 ` Phillip Potter
2021-08-23 22:26 ` Phillip Potter
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=262ccda0-0aed-26e9-0585-e5376db86596@gmail.com \
--to=paskripkin@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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