From: Gaston Gonzalez <gascoar@gmail.com>
To: linux-staging@lists.linux.dev
Cc: gregkh@linuxfoundation.org, nsaenz@kernel.org,
stefan.wahren@i2se.com, arnd@arndb.de, dan.carpenter@oracle.com,
ojaswin98@gmail.com, amarjargal16@gmail.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, gascoar@gmail.com
Subject: [PATCH v2 3/8] staging: vchiq_core.h: fix CamelCase in function declaration
Date: Sun, 24 Oct 2021 18:25:19 -0300 [thread overview]
Message-ID: <20211024212524.370078-4-gascoar@gmail.com> (raw)
In-Reply-To: <20211024212524.370078-1-gascoar@gmail.com>
Renaming function declaration to avoid CamelCase use.
As this was already fixed in the function definition in commit
801b1aa002d3 ("staging: vc04_services: fix CamelCase"), the current
change make the names of the variables in the function definition and
declartion match.
Reported by checkpatch.pl
Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
---
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h
index 893b07698268..383c3bcf787e 100644
--- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h
+++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h
@@ -622,7 +622,7 @@ extern void
vchiq_set_conn_state(struct vchiq_state *state, enum vchiq_connstate newstate);
extern void
-vchiq_log_dump_mem(const char *label, uint32_t addr, const void *voidMem, size_t numBytes);
+vchiq_log_dump_mem(const char *label, uint32_t addr, const void *void_mem, size_t num_bytes);
extern enum vchiq_status vchiq_remove_service(unsigned int service);
--
2.33.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-24 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 21:25 [PATCH v2 0/8] vchiq_core: various style cleanups Gaston Gonzalez
2021-10-24 21:25 ` [PATCH v2 1/8] staging: vchiq_core: cleanup blank lines Gaston Gonzalez
2021-10-24 21:25 ` [PATCH v2 2/8] staging: vchiq_core: cleanup code alignment issues Gaston Gonzalez
2021-10-24 21:25 ` Gaston Gonzalez [this message]
2021-10-24 21:25 ` [PATCH v2 4/8] staging: vchiq_core.h: use preferred kernel types Gaston Gonzalez
2021-10-25 7:11 ` Greg KH
2021-10-24 21:25 ` [PATCH v2 5/8] staging: vchiq: drop trailing semicolon in macro definition Gaston Gonzalez
2021-10-24 21:25 ` [PATCH v2 6/8] staging: vchiq_core: drop extern prefix in function declarations Gaston Gonzalez
2021-10-24 21:25 ` [PATCH v2 7/8] staging: vchiq_core: cleanup lines that end with '(' or '[' Gaston Gonzalez
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=20211024212524.370078-4-gascoar@gmail.com \
--to=gascoar@gmail.com \
--cc=amarjargal16@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=nsaenz@kernel.org \
--cc=ojaswin98@gmail.com \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).