From: Marek Belisko <marek.belisko@gmail.com>
To: Greg Kroah-Hartman <gregkh@suse.de>,
Marek Belisko <marek.belisko@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: Marek Belisko <marek.belisko@gmail.com>
Subject: [PATCH 3/7] staging:ft1000: Remove APP_INFO_BLOCK typedef usage.
Date: Fri, 15 Oct 2010 14:13:00 +0200 [thread overview]
Message-ID: <1287144784-3359-3-git-send-email-marek.belisko@gmail.com> (raw)
In-Reply-To: <1287144784-3359-1-git-send-email-marek.belisko@gmail.com>
Signed-off-by: Marek Belisko <marek.belisko@gmail.com>
---
drivers/staging/ft1000/ft1000-usb/ft1000_usb.h | 27 +++++++++++------------
1 files changed, 13 insertions(+), 14 deletions(-)
diff --git a/drivers/staging/ft1000/ft1000-usb/ft1000_usb.h b/drivers/staging/ft1000/ft1000-usb/ft1000_usb.h
index 200f3c0..3fce7f6 100644
--- a/drivers/staging/ft1000/ft1000-usb/ft1000_usb.h
+++ b/drivers/staging/ft1000/ft1000-usb/ft1000_usb.h
@@ -77,19 +77,18 @@ struct dsp_init_msg {
} __attribute__ ((packed));
-typedef struct _APP_INFO_BLOCK
-{
- u32 nTxMsg; // DPRAM msg sent to DSP with app_id
- u32 nRxMsg; // DPRAM msg rcv from dsp with app_id
- u32 nTxMsgReject; // DPRAM msg rejected due to DSP doorbell set
- u32 nRxMsgMiss; // DPRAM msg dropped due to overflow
- struct fown_struct *fileobject;// Application's file object
- u16 app_id; // Application id
- int DspBCMsgFlag;
- int NumOfMsg; // number of messages queued up
- wait_queue_head_t wait_dpram_msg;
- struct list_head app_sqlist; // link list of msgs for applicaton on slow queue
-} APP_INFO_BLOCK, *PAPP_INFO_BLOCK;
+struct app_info_block {
+ u32 nTxMsg; // DPRAM msg sent to DSP with app_id
+ u32 nRxMsg; // DPRAM msg rcv from dsp with app_id
+ u32 nTxMsgReject; // DPRAM msg rejected due to DSP doorbell set
+ u32 nRxMsgMiss; // DPRAM msg dropped due to overflow
+ struct fown_struct *fileobject;// Application's file object
+ u16 app_id; // Application id
+ int DspBCMsgFlag;
+ int NumOfMsg; // number of messages queued up
+ wait_queue_head_t wait_dpram_msg;
+ struct list_head app_sqlist; // link list of msgs for applicaton on slow queue
+} __attribute__((packed));
typedef struct _PROV_RECORD {
struct list_head list;
@@ -582,7 +581,7 @@ typedef struct _FT1000_INFO {
u16 ProgConStat;
struct list_head prov_list;
int appcnt;
- APP_INFO_BLOCK app_info[MAX_NUM_APP]; //Added by Jim
+ struct app_info_block app_info[MAX_NUM_APP];
u16 DSPInfoBlklen;
u16 DrvMsgPend;
int (*ft1000_reset)(struct net_device *dev);
--
1.7.1
next prev parent reply other threads:[~2010-10-15 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 12:12 [PATCH 1/7] staging:ft1000: Remove MEDIAMSG " Marek Belisko
2010-10-15 12:12 ` [PATCH 2/7] staging:ft1000: Remove DSPINITMSG " Marek Belisko
2010-10-15 12:13 ` Marek Belisko [this message]
2010-10-15 12:13 ` [PATCH 4/7] staging:ft1000: Remove PROV_RECORD " Marek Belisko
2010-10-15 12:13 ` [PATCH 5/7] staging:ft1000: Remove PSEUDO_HDR " Marek Belisko
2010-10-15 12:13 ` [PATCH 6/7] staging:ft1000: Remove DRVMGS " Marek Belisko
2010-10-15 12:13 ` [PATCH 7/7] staging:ft1000: Remove FT1000_INFO " Marek Belisko
2010-10-15 19:40 ` [PATCH 7/7] staging: ft1000: " Greg KH
2010-10-15 20:16 ` Belisko Marek
2010-10-15 21:12 ` Greg KH
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=1287144784-3359-3-git-send-email-marek.belisko@gmail.com \
--to=marek.belisko@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome