All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Shareef <jamal.k.shareef@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: eric@anholt.net, wahrenst@gmx.net, gregkh@linuxfoundation.org,
	Jamal Shareef <jamal.k.shareef@gmail.com>
Subject: [PATCH 14/14] staging: vc04_services: Remove platform typedef
Date: Mon,  4 Nov 2019 16:55:24 -0800	[thread overview]
Message-ID: <e65f802b6cff5af1630dc395d666e4b49356d29b.1572915104.git.jamal.k.shareef@gmail.com> (raw)
In-Reply-To: <cover.1572915104.git.jamal.k.shareef@gmail.com>
In-Reply-To: <cover.1572915104.git.jamal.k.shareef@gmail.com>

Removes opaque platform struct typedef. Issue found by checkpatch.

Signed-off-by: Jamal Shareef <jamal.k.shareef@gmail.com>
---
 .../staging/vc04_services/interface/vchiq_arm/vchiq_core.h    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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 05b39c3564f6..419bcdd165b4 100644
--- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h
+++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h
@@ -236,7 +236,7 @@ struct remote_event {
 	u32 __unused;
 };
 
-typedef struct opaque_platform_state_t *VCHIQ_PLATFORM_STATE_T;
+struct opaque_platform_state;
 
 struct vchiq_slot {
 	char data[VCHIQ_SLOT_SIZE];
@@ -468,7 +468,7 @@ struct vchiq_state {
 	struct vchiq_service_quota service_quotas[VCHIQ_MAX_SERVICES];
 	struct vchiq_slot_info slot_info[VCHIQ_MAX_SLOTS];
 
-	VCHIQ_PLATFORM_STATE_T platform_state;
+	struct opaque_platform_state *platform_state;
 };
 
 struct bulk_waiter {
-- 
2.17.1



      parent reply	other threads:[~2019-11-05  0:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  0:55 [PATCH 00/14] staging: vc04_services: Remove typedefs Jamal Shareef
2019-11-05  0:55 ` [PATCH 01/14] staging: vc04_services: Remove instance struct typedef Jamal Shareef
2019-11-05 17:13   ` Greg KH
2019-11-05  0:55 ` [PATCH 02/14] staging: vc04_services: Remove service " Jamal Shareef
2019-11-05  0:55 ` [PATCH 03/14] staging: vc04_services: Rename function pointer typedef Jamal Shareef
2019-11-05  0:55 ` [PATCH 04/14] staging: vc04_services: Remove status enum typedef Jamal Shareef
2019-11-05  0:55 ` [PATCH 05/14] staging: vc04_services: Remove bulk mode " Jamal Shareef
2019-11-05  0:55 ` [PATCH 06/14] staging: vc04_services: Remove option " Jamal Shareef
2019-11-05  0:55 ` [PATCH 07/14] staging: vc04_services: Remove connstate " Jamal Shareef
2019-11-05  0:55 ` [PATCH 08/14] staging: vc04_services: Remove bulk dir " Jamal Shareef
2019-11-05  0:55 ` [PATCH 09/14] staging: vc04_services: Rename userdata callback Jamal Shareef
2019-11-05  0:55 ` [PATCH 10/14] staging: vc04_services: Rename vchiq callback Jamal Shareef
2019-11-05  0:55 ` [PATCH 11/14] staging: vc04_services: Rename remote use callback Jamal Shareef
2019-11-05  0:55 ` [PATCH 12/14] staging: vc04_services: Remove int typedef Jamal Shareef
2019-11-05  0:55 ` [PATCH 13/14] staging: vc04_services: Remove vchiq instance typedef Jamal Shareef
2019-11-05  0:55 ` Jamal Shareef [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=e65f802b6cff5af1630dc395d666e4b49356d29b.1572915104.git.jamal.k.shareef@gmail.com \
    --to=jamal.k.shareef@gmail.com \
    --cc=eric@anholt.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=wahrenst@gmx.net \
    /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.