From: Alexon Oliveira <alexondunkan@gmail.com>
To: gregkh@linuxfoundation.org
Cc: martyn@welchs.me.uk, manohar.vanga@gmail.com,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
Alexon Oliveira <alexondunkan@gmail.com>
Subject: [PATCH v4 4/4] staging: vme_user: fix check unnecessary space after a cast in vme_fake.c
Date: Sun, 27 Aug 2023 16:32:55 -0300 [thread overview]
Message-ID: <603976b29ad4d9a0e4cbd8452ff674ec70a227a8.1693164540.git.alexondunkan@gmail.com> (raw)
In-Reply-To: <cover.1693164540.git.alexondunkan@gmail.com>
Fixed all CHECK: No space is necessary after a cast
as reported by checkpatch to adhere to the Linux kernel
coding-style guidelines.
Signed-off-by: Alexon Oliveira <alexondunkan@gmail.com>
---
Changes in v2:
- Fixed summary phrase with tags to indicate commit order
in the patch series, noted by Greg KH
Changes in v3:
- Sent patch series in a single email thread, noted by Nam Cao
Changes in v4:
- Versioning the patch series with the forgotten information
about the changes in the previous versions, noted by Greg KH
drivers/staging/vme_user/vme_fake.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/vme_user/vme_fake.c b/drivers/staging/vme_user/vme_fake.c
index 4258ed6033e7..4ccb16dd0d0b 100644
--- a/drivers/staging/vme_user/vme_fake.c
+++ b/drivers/staging/vme_user/vme_fake.c
@@ -95,7 +95,7 @@ static void fake_VIRQ_tasklet(unsigned long data)
struct vme_bridge *fake_bridge;
struct fake_driver *bridge;
- fake_bridge = (struct vme_bridge *) data;
+ fake_bridge = (struct vme_bridge *)data;
bridge = fake_bridge->driver_priv;
vme_irq_handler(fake_bridge, bridge->int_level, bridge->int_statid);
@@ -1092,7 +1092,7 @@ static int __init fake_init(void)
mutex_init(&fake_device->vme_int);
mutex_init(&fake_bridge->irq_mtx);
tasklet_init(&fake_device->int_tasklet, fake_VIRQ_tasklet,
- (unsigned long) fake_bridge);
+ (unsigned long)fake_bridge);
strcpy(fake_bridge->name, driver_name);
--
2.41.0
prev parent reply other threads:[~2023-08-27 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 19:32 [PATCH v4 0/4] staging: vme_user: fix checks reported in vme_fake.c Alexon Oliveira
2023-08-27 19:32 ` [PATCH v4 1/4] staging: vme_user: fix check alignment of open parenthesis " Alexon Oliveira
2023-08-27 19:32 ` [PATCH v4 2/4] staging: vme_user: fix check lines not ending with '(' " Alexon Oliveira
2023-08-27 19:32 ` [PATCH v4 3/4] staging: vme_user: fix check unnecessary blank lines " Alexon Oliveira
2023-08-27 19:32 ` Alexon Oliveira [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=603976b29ad4d9a0e4cbd8452ff674ec70a227a8.1693164540.git.alexondunkan@gmail.com \
--to=alexondunkan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
/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).