From: Nam Cao <namcaov@gmail.com>
To: forest@alittletooquiet.net, gregkh@linuxfoundation.org
Cc: namcaov@gmail.com, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: [PATCH v3 1/2] staging: vt6655: remove unnecessary volatile qualifier
Date: Fri, 9 Sep 2022 14:17:55 +0200 [thread overview]
Message-ID: <c3a7d9963b1c38c5f493786d7268c430617412dd.1662724786.git.namcaov@gmail.com> (raw)
In-Reply-To: <cover.1662724786.git.namcaov@gmail.com>
Remove volatile qualifier for the member rd0 of struct vnt_rx_desc,
because there is no reason it must be volatile.
Signed-off-by: Nam Cao <namcaov@gmail.com>
---
drivers/staging/vt6655/desc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/vt6655/desc.h b/drivers/staging/vt6655/desc.h
index 17a40c53b8ff..3f0f287b1693 100644
--- a/drivers/staging/vt6655/desc.h
+++ b/drivers/staging/vt6655/desc.h
@@ -182,7 +182,7 @@ struct vnt_rdes1 {
/* Rx descriptor*/
struct vnt_rx_desc {
- volatile struct vnt_rdes0 rd0;
+ struct vnt_rdes0 rd0;
volatile struct vnt_rdes1 rd1;
volatile __le32 buff_addr;
volatile __le32 next_desc;
--
2.25.1
next prev parent reply other threads:[~2022-09-09 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 12:17 [PATCH v3 0/2] use memset to make code clearer Nam Cao
2022-09-09 12:17 ` Nam Cao [this message]
2022-09-09 18:03 ` [PATCH v3 1/2] staging: vt6655: remove unnecessary volatile qualifier 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 ` [PATCH v3 0/2] " Philipp Hortmann
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=c3a7d9963b1c38c5f493786d7268c430617412dd.1662724786.git.namcaov@gmail.com \
--to=namcaov@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).