From: Kevin McKinney <klmckinney1@gmail.com>
To: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Cc: dan.carpenter@oracle.com, Kevin McKinney <klmckinney1@gmail.com>
Subject: [PATCH 08/11] Staging: bcm: Replace UINT32 with u32 in Adapter.h
Date: Sat, 26 Oct 2013 02:15:17 -0400 [thread overview]
Message-ID: <1382768120-23380-8-git-send-email-klmckinney1@gmail.com> (raw)
In-Reply-To: <1382768120-23380-1-git-send-email-klmckinney1@gmail.com>
This patch replaces "UINT32" with "u32"
in Adapter.h
Signed-off-by: Kevin McKinney <klmckinney1@gmail.com>
---
drivers/staging/bcm/Adapter.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/bcm/Adapter.h b/drivers/staging/bcm/Adapter.h
index 27b5011..eeeea34 100644
--- a/drivers/staging/bcm/Adapter.h
+++ b/drivers/staging/bcm/Adapter.h
@@ -94,7 +94,7 @@ struct bcm_classifier_rule {
/* For IPv6 Addressing */
unsigned char ucDirection;
BOOLEAN bIpv6Protocol;
- UINT32 u32PHSRuleID;
+ u32 u32PHSRuleID;
struct bcm_phs_rule sPhsRule;
unsigned char u8AssociatedPHSI;
@@ -340,11 +340,11 @@ struct bcm_mini_adapter {
BOOLEAN AutoFirmDld;
BOOLEAN bMipsConfig;
BOOLEAN bDPLLConfig;
- UINT32 aTxPktSizeHist[MIBS_MAX_HIST_ENTRIES];
- UINT32 aRxPktSizeHist[MIBS_MAX_HIST_ENTRIES];
+ u32 aTxPktSizeHist[MIBS_MAX_HIST_ENTRIES];
+ u32 aRxPktSizeHist[MIBS_MAX_HIST_ENTRIES];
struct bcm_fragmented_packet_info astFragmentedPktClassifierTable[MAX_FRAGMENTEDIP_CLASSIFICATION_ENTRIES];
atomic_t uiMBupdate;
- UINT32 PmuMode;
+ u32 PmuMode;
enum bcm_nvm_type eNVMType;
UINT uiSectorSize;
UINT uiSectorSizeInCFG;
@@ -388,7 +388,7 @@ struct bcm_mini_adapter {
BOOLEAN bDoSuspend;
UINT syscfgBefFwDld;
BOOLEAN StopAllXaction;
- UINT32 liTimeSinceLastNetEntry; /* Used to Support extended CAPI requirements from */
+ u32 liTimeSinceLastNetEntry; /* Used to Support extended CAPI requirements from */
struct semaphore LowPowerModeSync;
unsigned long liDrainCalculated;
UINT gpioBitMap;
--
1.7.9.5
next prev parent reply other threads:[~2013-10-26 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 6:15 [PATCH 01/11] Staging: bcm: Fix WARNING: space prohibited before semicolon Kevin McKinney
2013-10-26 6:15 ` [PATCH 02/11] Staging: bcm: Remove typedef for _U_IP_ADDRESS and call directly Kevin McKinney
2013-10-26 6:15 ` [PATCH 03/11] Staging: bcm: Replace USHORT with unsigned short in Adapter.h Kevin McKinney
2013-10-26 6:15 ` [PATCH 04/11] Staging: bcm: Replace UCHAR with unsigned char " Kevin McKinney
2013-10-27 8:25 ` Dan Carpenter
2013-10-27 23:55 ` Kevin McKinney
2013-10-26 6:15 ` [PATCH 05/11] Staging: bcm: Replace ULONG with unsigned long " Kevin McKinney
2013-10-27 8:20 ` Dan Carpenter
2013-10-26 6:15 ` [PATCH 06/11] Staging: bcm: Replace B_UINT16 with u16 " Kevin McKinney
2013-10-26 6:15 ` [PATCH 07/11] Staging: bcm: Replace B_UINT8 with u8 " Kevin McKinney
2013-10-26 6:15 ` Kevin McKinney [this message]
2013-10-26 6:15 ` [PATCH 09/11] Staging: bcm: Replace UINT with unsigned int " Kevin McKinney
2013-10-26 6:15 ` [PATCH 10/11] Staging: bcm: Replace PVOID with void * " Kevin McKinney
2013-10-26 6:15 ` [PATCH 11/11] Staging: bcm: Replace BOOLEAN with bool " Kevin McKinney
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=1382768120-23380-8-git-send-email-klmckinney1@gmail.com \
--to=klmckinney1@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).