From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Nam Cao <namcaov@gmail.com>,
forest@alittletooquiet.net, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v3 0/2] use memset to make code clearer
Date: Fri, 9 Sep 2022 19:58:37 +0200 [thread overview]
Message-ID: <2b19f1b0-0916-9fe7-99a4-33d0c626b7c3@gmail.com> (raw)
In-Reply-To: <cover.1662724786.git.namcaov@gmail.com>
On 9/9/22 14:17, Nam Cao wrote:
> Re-write some code using memset to make it more obvious. Also remove an
> unnecessary volatile qualifier, because compiler complains about passing
> volatile pointer to memset.
>
> V3: get rid of "volatile" entirely, instead of just casting it away.
> V2: re-write commit message because previous message describes a
> non-existent problem.
>
> Nam Cao (2):
> staging: vt6655: remove unnecessary volatile qualifier
> staging: vt6655: use memset to make code clearer
>
> drivers/staging/vt6655/desc.h | 2 +-
> drivers/staging/vt6655/device_main.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
prev parent reply other threads:[~2022-09-09 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 12:17 Nam Cao
2022-09-09 12:17 ` [PATCH v3 1/2] staging: vt6655: remove unnecessary volatile qualifier Nam Cao
2022-09-09 18:03 ` Greg KH
2022-09-11 7:12 ` Nam Cao
2022-09-11 7:25 ` Greg KH
2022-09-13 16:52 ` Nam Cao
2022-09-14 8:02 ` Greg KH
2022-09-09 12:17 ` [PATCH v3 2/2] staging: vt6655: use memset to make code clearer Nam Cao
2022-09-09 17:58 ` Philipp Hortmann [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=2b19f1b0-0916-9fe7-99a4-33d0c626b7c3@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=namcaov@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®