From: Greg KH <gregkh@linuxfoundation.org>
To: Deepak R Varma <drv@mailo.com>
Cc: outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: most: dim2: read done_buffers count locally from HDM channel
Date: Tue, 18 Oct 2022 19:12:45 +0200 [thread overview]
Message-ID: <Y07ejaO8vrtPU5JX@kroah.com> (raw)
In-Reply-To: <83fd237d2ac157d234e9c7cce1206904c2d8773d.1666105876.git.drv@mailo.com>
On Tue, Oct 18, 2022 at 10:19:21PM +0530, Deepak R Varma wrote:
> The function dim_get_channel_state only serves to initialize the ready and
> done_buffers fields of the structure passed as its second argument. In
> service_done_flag, this structure is never used again and the only purpose
> of the call is to get the value that is put in the done_buffers field.
> But that value is just the done_sw_buffers_number field of the call's
> first argument. So the whole call is useless, and we can just replace it
> with an access to this field.
>
> This change implies that the variable st is no longer used, so drop it as
> well.
>
> Signed-off-by: Deepak R Varma <drv@mailo.com>
> ---
>
> PLEASE NOTE:
> 1. I have only built the module on my machine, but have not tested it.
> I am not sure how to test this change. I am willing to test it with
> appropriate guidance provided I have the necessary hardware.
> 2. This was a standalone patch earlier. It is now combined into a patch set
> with another patch for the same driver. Hence I am carry forwarding the
> change log for this patch here:
>
> Changes in v3:
> 1. The patch log message is further improved. This revised verbiage is as
> thankfully provided by julia.lawall@inria.fr
>
> Changes in v2:
> 1. Update patch log message to be more descriptive about the reason for change.
> Feedback provided by julia.lawall@inria.fr
>
You need to say this is a v3 in the subject line as documented :(
next prev parent reply other threads:[~2022-10-18 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 16:48 [PATCH 0/2] staging: most: dim2: remove unnecessary function call and variable usage Deepak R Varma
2022-10-18 16:49 ` [PATCH 1/2] staging: most: dim2: read done_buffers count locally from HDM channel Deepak R Varma
2022-10-18 17:12 ` Greg KH [this message]
2022-10-18 17:40 ` Deepak R Varma
2022-10-18 18:07 ` Greg KH
2022-10-18 16:49 ` [PATCH 2/2] staging: most: dim2: correct misleading variable name Deepak R Varma
2022-10-18 16:59 ` Julia Lawall
2022-10-18 17:41 ` Deepak R Varma
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=Y07ejaO8vrtPU5JX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=drv@mailo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.