From: Deepak R Varma <drv@mailo.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: outreachy@lists.linux.dev, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
kumarpraveen@linux.microsoft.com, saurabh.truth@gmail.com
Subject: Re: [PATCH v4 2/2] staging: most: dim2: correct misleading struct type name
Date: Thu, 20 Oct 2022 18:26:12 +0530 [thread overview]
Message-ID: <Y1FFbB8BWi1IHYgB@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <404cc67c-efd6-4a70-c3ca-7958db21bcb@inria.fr>
On Thu, Oct 20, 2022 at 02:06:41PM +0200, Julia Lawall wrote:
>
>
> On Thu, 20 Oct 2022, Deepak R Varma wrote:
>
> > On Thu, Oct 20, 2022 at 02:00:29AM +0530, Deepak R Varma wrote:
> > > On Wed, Oct 19, 2022 at 10:08:53PM +0200, Julia Lawall wrote:
> > > >
> > > >
> > > > On Thu, 20 Oct 2022, Deepak R Varma wrote:
> > > >
> > > > > Correct misleading struct type name dim_ch_state_t to dim_ch_state
> > > > > since this not a typedef but a normal structure declaration.
> > > > >
> > > > > Suggested-by: Julia Lawall <julia.lawall@inria.fr>
> > > > > Signed-off-by: Deepak R Varma <drv@mailo.com>
> > > > > ---
> > > > >
> > > > > Changes in v4:
> > > > > 1. Correct patch subject and log message. Use struct type name instead of
> > > > > variable name for the change description. Feedback from julia.lawall@inria.fr
> > > > >
> > > > > Changes in v3:
> > > > > 1. Patch introduced in the patch set
> > > > >
> > > > > drivers/staging/most/dim2/dim2.c | 2 +-
> > > > > drivers/staging/most/dim2/hal.c | 4 ++--
> > > > > drivers/staging/most/dim2/hal.h | 6 +++---
> > > > > 3 files changed, 6 insertions(+), 6 deletions(-)
> > > > >
> > > > > diff --git a/drivers/staging/most/dim2/dim2.c b/drivers/staging/most/dim2/dim2.c
> > > > > index 4c1f27898a29..a69a61a69283 100644
> > > > > --- a/drivers/staging/most/dim2/dim2.c
> > > > > +++ b/drivers/staging/most/dim2/dim2.c
> > > > > @@ -161,7 +161,7 @@ static int try_start_dim_transfer(struct hdm_channel *hdm_ch)
> > > > > struct list_head *head = &hdm_ch->pending_list;
> > > > > struct mbo *mbo;
> > > > > unsigned long flags;
> > > > > - struct dim_ch_state_t st;
> > > > > + struct dim_ch_state st;
> > > >
> > > > Is there another use in service_done_flag?
> > >
> > > Hi,
> > > I did not understand your question fully. This is from a different function
> > > try_start_dim_transfer where the variable st is used down the line in the
> > > execution. This time the channel state is retrieved by calling
> > > dim_get_channel_state function. The state is simply computed and set. Should I
> > > improve this as well?
> > >
> > > If you are asking something different, could you please elaborate?
> >
> > Hi Julia,
> > Can you please review and comment on my response?
>
> In my kernel there is an occurrence of the type name in service_done_flag.
> But I have the mainline, not Greg's staging tree, so there could be some
> differences.
>
> When I do git grep dim_ch_state_t, I get two occurrences in
> drivers/staging/most/dim2/dim2.c
Okay. Still unclear. Following snip is what I see in my local staging-testing branch.
<snip>
drv@debian:~/git/kernels/staging$ git grep dim_ch_state_t
drivers/staging/most/dim2/dim2.c: struct dim_ch_state_t st;
drivers/staging/most/dim2/dim2.c: struct dim_ch_state_t st;
drivers/staging/most/dim2/hal.c:struct dim_ch_state_t *dim_get_channel_state(struct dim_channel *ch,
drivers/staging/most/dim2/hal.c: struct dim_ch_state_t *state_ptr)
drivers/staging/most/dim2/hal.h:struct dim_ch_state_t {
drivers/staging/most/dim2/hal.h:struct dim_ch_state_t *dim_get_channel_state(struct dim_channel *ch,
drivers/staging/most/dim2/hal.h: struct dim_ch_state_t *state_ptr);
drv@debian:~/git/kernels/staging$
</snip>
Does that help?
./drv
>
> julia
next prev parent reply other threads:[~2022-10-20 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 19:53 [PATCH v4 0/2] staging: most: dim2: remove unnecessary function call and variable usage Deepak R Varma
2022-10-19 19:54 ` [PATCH v4 1/2] staging: most: dim2: read done_buffers count locally from HDM channel Deepak R Varma
2022-10-20 15:03 ` Greg KH
2022-10-20 16:41 ` Deepak R Varma
2022-10-19 19:56 ` [PATCH v4 2/2] staging: most: dim2: correct misleading struct type name Deepak R Varma
2022-10-19 20:08 ` Julia Lawall
2022-10-19 20:30 ` Deepak R Varma
2022-10-20 11:48 ` Deepak R Varma
2022-10-20 12:06 ` Julia Lawall
2022-10-20 12:56 ` Deepak R Varma [this message]
2022-10-20 15:04 ` Greg KH
2022-10-20 15:05 ` Greg KH
2022-10-20 15:10 ` Julia Lawall
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=Y1FFbB8BWi1IHYgB@debian-BULLSEYE-live-builder-AMD64 \
--to=drv@mailo.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=kumarpraveen@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=saurabh.truth@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
all inboxes | Powered by JetHome®