From: Bixuan Cui <cuibixuan@huawei.com>
To: Ian Abbott <abbotti@mev.co.uk>, <linux-kernel@vger.kernel.org>
Cc: <hsweeten@visionengravers.com>, <gregkh@linuxfoundation.org>,
<grandmaster@al2klimov.de>
Subject: Re: [PATCH -next v2] staging: comedi: Remove unused variable ‘min_full_scale’ and function 'get_min_full_scales'
Date: Wed, 19 May 2021 09:07:16 +0800 [thread overview]
Message-ID: <a21ada45-8eb8-88b7-7634-096487efc81e@huawei.com> (raw)
In-Reply-To: <517e8f75-3faa-b564-5252-d5a3812f15f9@mev.co.uk>
On 2021/5/17 17:44, Ian Abbott wrote:
> On 14/05/2021 09:52, Bixuan Cui wrote:
>> The variable ‘min_full_scale’ and function 'get_min_full_scales' are
>> not used, So delete them.
>>
>> Signed-off-by: Bixuan Cui <cuibixuan@huawei.com>
>> ---
>> Changes from v2:
>> * Delete function 'get_min_full_scales'
>>
>> drivers/comedi/drivers/jr3_pci.c | 15 ---------------
>> 1 file changed, 15 deletions(-)
>>
>> diff --git a/drivers/comedi/drivers/jr3_pci.c b/drivers/comedi/drivers/jr3_pci.c
>> index 7a02c4fa3cda..f963080dd61f 100644
>> --- a/drivers/comedi/drivers/jr3_pci.c
>> +++ b/drivers/comedi/drivers/jr3_pci.c
>> @@ -186,19 +186,6 @@ static void set_full_scales(struct jr3_sensor __iomem *sensor,
>> set_s16(&sensor->command_word0, 0x0a00);
>> }
>> -static struct six_axis_t get_min_full_scales(struct jr3_sensor __iomem *sensor)
>> -{
>> - struct six_axis_t result;
>> -
>> - result.fx = get_s16(&sensor->min_full_scale.fx);
>> - result.fy = get_s16(&sensor->min_full_scale.fy);
>> - result.fz = get_s16(&sensor->min_full_scale.fz);
>> - result.mx = get_s16(&sensor->min_full_scale.mx);
>> - result.my = get_s16(&sensor->min_full_scale.my);
>> - result.mz = get_s16(&sensor->min_full_scale.mz);
>> - return result;
>> -}
>> -
>> static struct six_axis_t get_max_full_scales(struct jr3_sensor __iomem *sensor)
>> {
>> struct six_axis_t result;
>> @@ -504,10 +491,8 @@ jr3_pci_poll_subdevice(struct comedi_subdevice *s)
>> result = poll_delay_min_max(20, 100);
>> } else {
>> /* Set full scale */
>> - struct six_axis_t min_full_scale;
>> struct six_axis_t max_full_scale;
>> - min_full_scale = get_min_full_scales(sensor);
>> max_full_scale = get_max_full_scales(sensor);
>> set_full_scales(sensor, max_full_scale);
>>
>
> I'm pretty sure this is OK. The min_full_scale registers are just informational. The driver used to print the values, but not since commit a1d16659538a ("staging: comedi: jr3_pci: remove noisy printk") so this code is now redundant.
Thanks for your reply.
Thanks
Bixuan Cui
>
> Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
>
prev parent reply other threads:[~2021-05-19 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 8:52 Bixuan Cui
2021-05-14 7:52 ` Greg KH
2021-05-14 11:16 ` Ian Abbott
2021-05-14 11:54 ` Greg KH
2021-05-17 9:44 ` Ian Abbott
2021-05-19 1:07 ` Bixuan Cui [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=a21ada45-8eb8-88b7-7634-096487efc81e@huawei.com \
--to=cuibixuan@huawei.com \
--cc=abbotti@mev.co.uk \
--cc=grandmaster@al2klimov.de \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®