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 v4 0/8] staging: vc04_services: Remove typedefs
Date: Fri, 1 Nov 2019 17:04:12 -0700 [thread overview]
Message-ID: <cover.1572652827.git.jamal.k.shareef@gmail.com> (raw)
This patch removes typedefs from vc04_services files.
Changes in v4:
- Place removal of VCHIQ_USERDATA_TERM_T callback into callback patch
(Patch 6). Was in struct patch (Patch 8) previously.
Changes in v3:
- Separate removal of unused opaque struct typedefs that were remaining
in the vchi enum typedef patch to a separate patch (now Patch 1).
- Remove formatting in vchi enum typedef Patch 2 which was better
served in Patch 3.
Changes in v2:
- Split patches into smaller patches limitied to typedef type.
Patch 8:
- Rename "struct vchiq_instance_struct' to "struct vchiq_instance" due
to wordiness and agreement between header files.
Jamal Shareef (8):
staging: vc04_services: Remove unused structs
staging: vc04_services: Remove enum typedefs in vchi
staging: vc04_services: Remove struct typedefs in vchi
staging: vc04_services: Remove function pointer typedef
staging: vc04_services: Remove vchiq_arm enum typedefs
staging: vc04_services: Remove callback typedef
staging: vc04_services: Remove int typedef
staging: vc04_services: Remove struct typedefs vchiq_arm
.../bcm2835-audio/bcm2835-vchiq.c | 6 +-
.../vc04_services/bcm2835-audio/bcm2835.h | 2 +-
.../vc04_services/bcm2835-camera/mmal-vchiq.c | 6 +-
.../vc04_services/interface/vchi/vchi.h | 78 ++++----
.../interface/vchi/vchi_common.h | 27 +--
.../interface/vchiq_arm/vchiq_2835_arm.c | 10 +-
.../interface/vchiq_arm/vchiq_arm.c | 170 ++++++++---------
.../interface/vchiq_arm/vchiq_arm.h | 32 ++--
.../interface/vchiq_arm/vchiq_core.c | 116 ++++++------
.../interface/vchiq_arm/vchiq_core.h | 90 +++++----
.../interface/vchiq_arm/vchiq_debugfs.c | 14 +-
.../interface/vchiq_arm/vchiq_debugfs.h | 4 +-
.../interface/vchiq_arm/vchiq_if.h | 92 +++++----
.../interface/vchiq_arm/vchiq_ioctl.h | 4 +-
.../interface/vchiq_arm/vchiq_shim.c | 177 +++++++++---------
15 files changed, 405 insertions(+), 423 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-02 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 0:04 Jamal Shareef [this message]
2019-11-02 0:04 ` [PATCH v4 1/8] staging: vc04_services: Remove unused structs Jamal Shareef
2019-11-02 0:04 ` [PATCH v4 2/8] staging: vc04_services: Remove enum typedefs in vchi Jamal Shareef
2019-11-02 0:04 ` [PATCH v4 3/8] staging: vc04_services: Remove struct " Jamal Shareef
2019-11-02 10:38 ` Greg KH
2019-11-02 0:04 ` [PATCH v4 4/8] staging: vc04_services: Remove function pointer typedef Jamal Shareef
2019-11-02 0:04 ` [PATCH v4 5/8] staging: vc04_services: Remove vchiq_arm enum typedefs Jamal Shareef
2019-11-02 0:04 ` [PATCH v4 6/8] staging: vc04_services: Remove callback typedef Jamal Shareef
2019-11-02 10:32 ` Greg KH
2019-11-02 0:04 ` [PATCH v4 7/8] staging: vc04_services: Remove int typedef Jamal Shareef
2019-11-02 0:04 ` [PATCH v4 8/8] staging: vc04_services: Remove struct typedefs vchiq_arm Jamal Shareef
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=cover.1572652827.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.