From: Aishwarya Pant <aishpant@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: gregkh@linuxfoundation.org
Subject: [PATCH 0/2] staging: vc04_services: clean up anonymous field declarations
Date: Fri, 10 Mar 2017 22:08:33 +0530 [thread overview]
Message-ID: <cover.1489163547.git.aishpant@gmail.com> (raw)
This patchset replaces anonymous field declarations for the typedef
SERVICE_CREATION_T with explicit field declarations in the drivers
bcm2835-audio and bcm2835-camera.
typedef struct {
struct vchi_version version;
int32_t service_id;
VCHI_CONNECTION_T *connection;
uint32_t rx_fifo_size;
uint32_t tx_fifo_size;
VCHI_CALLBACK_T callback;
void *callback_param;
/* client intends to receive bulk transfers of
odd lengths or into unaligned buffers */
int32_t want_unaligned_bulk_rx;
/* client intends to transmit bulk transfers of
odd lengths or out of unaligned buffers */
int32_t want_unaligned_bulk_tx;
/* client wants to check CRCs on (bulk) xfers.
Only needs to be set at 1 end - will do both directions. */
int32_t want_crc;
} SERVICE_CREATION_T;
** HERE ***
Aishwarya Pant (2):
staging: bcm2835-audio: remove anonymous field declarations
staging: bcm2835-camera: remove anonymous field declarations
.../vc04_services/bcm2835-audio/bcm2835-vchiq.c | 20 ++++++++++----------
.../vc04_services/bcm2835-camera/mmal-vchiq.c | 20 ++++++++++----------
2 files changed, 20 insertions(+), 20 deletions(-)
--
2.7.4
next reply other threads:[~2017-03-10 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 16:38 Aishwarya Pant [this message]
2017-03-10 16:39 ` [PATCH 1/2] staging: bcm2835-audio: remove anonymous field declarations Aishwarya Pant
2017-03-10 16:58 ` [Outreachy kernel] " Julia Lawall
2017-03-10 16:39 ` [PATCH 2/2] staging: bcm2835-camera: " Aishwarya Pant
2017-03-10 16:50 ` [Outreachy kernel] " Julia Lawall
2017-03-10 17:08 ` Aishwarya Pant
2017-03-10 17:22 ` Julia Lawall
2017-03-10 17:00 ` [Outreachy kernel] [PATCH 0/2] staging: vc04_services: clean up " Julia Lawall
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.1489163547.git.aishpant@gmail.com \
--to=aishpant@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.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 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.