All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepak R Varma <drv@mailo.com>
To: outreachy@lists.linux.dev, gregkh@linuxfoundation.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: kumarpraveen@linux.microsoft.com, saurabh.truth@gmail.com
Subject: [PATCH v4 0/2] staging: most: dim2: remove unnecessary function call and variable usage
Date: Thu, 20 Oct 2022 01:23:20 +0530	[thread overview]
Message-ID: <cover.1666208065.git.drv@mailo.com> (raw)

Patch set simplifies service_done_flag function by eliminating call to
dim_get_channel_state. Also corrects the misleading dim_ch_state_t variable
type name.

Changes in v4:
   1. Patch set versioning missed earlier. Now added. [feedback from gregkh@linuxfoundation.org]
   2. Patch 1/2 : None.
   3. Patch 2/2 : Correct patch subject and log. [feedback from julia.lawall@inria.fr]

Change in v3:
   1. Patch set introduced since another patch from same area added.


Deepak R Varma (2):
  staging: most: dim2: read done_buffers count locally from HDM channel
  staging: most: dim2: correct misleading struct type name

 drivers/staging/most/dim2/dim2.c | 5 ++---
 drivers/staging/most/dim2/hal.c  | 4 ++--
 drivers/staging/most/dim2/hal.h  | 6 +++---
 3 files changed, 7 insertions(+), 8 deletions(-)

--
2.30.2




             reply	other threads:[~2022-10-19 19:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 19:53 Deepak R Varma [this message]
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
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=cover.1666208065.git.drv@mailo.com \
    --to=drv@mailo.com \
    --cc=gregkh@linuxfoundation.org \
    --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 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.