[PATCH 2/3] Drivers: Staging: cxt1e1: sbeid: Fixed braces coding style issue

From: Eric Skoglund
Date: Tue Nov 12 2013 - 04:43:38 EST


From: Eric Skoglund <eric@xxxxxxxxxxxx>

This patch fixes a brace coding style issue.

Signed-off-by: Eric Skoglund <eric@xxxxxxxxxxxx>
---
drivers/staging/cxt1e1/sbeid.c | 15 +++++----------
1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/drivers/staging/cxt1e1/sbeid.c b/drivers/staging/cxt1e1/sbeid.c
index 75efbc3..bf6c943 100644
--- a/drivers/staging/cxt1e1/sbeid.c
+++ b/drivers/staging/cxt1e1/sbeid.c
@@ -24,8 +24,7 @@ sbeid_get_bdname (ci_t *ci)
{
char *np = NULL;

- switch (ci->brd_id)
- {
+ switch (ci->brd_id) {
case SBE_BOARD_ID (PCI_VENDOR_ID_SBE, PCI_DEVICE_ID_WANPTMC_256T3_E1):
np = "wanPTMC-256T3 <E1>";
break;
@@ -73,8 +72,7 @@ sbeid_set_hdwbid (ci_t *ci)
* have this register implemented)
*/

- switch (ci->brd_id)
- {
+ switch (ci->brd_id) {
case SBE_BOARD_ID (PCI_VENDOR_ID_SBE, PCI_DEVICE_ID_WANPTMC_256T3_E1):
ci->hdw_bid = SBE_BID_256T3_E1; /* 0x46 - SBE wanPTMC-256T3 (E1
* Version) */
@@ -89,8 +87,7 @@ sbeid_set_hdwbid (ci_t *ci)
* This Board ID is a generic identification. Use the found number
* of ports to further define this hardware.
*/
- switch (ci->max_port)
- {
+ switch (ci->max_port) {
default: /* shouldn't need a default, but have one
* anyway */
case 4:
@@ -130,8 +127,7 @@ sbeid_set_hdwbid (ci_t *ci)
* This Board ID is a generic identification. Use the number of
* found ports to further define this hardware.
*/
- switch (ci->max_port)
- {
+ switch (ci->max_port) {
default: /* shouldn't need a default, but have one
* anyway */
case 4:
@@ -166,8 +162,7 @@ void
sbeid_set_bdtype (ci_t *ci)
{
/* set SBE's unique PCI VENDOR/DEVID */
- switch (ci->hdw_bid)
- {
+ switch (ci->hdw_bid) {
case SBE_BID_C1T3: /* SBE wanPMC-C1T3 */
ci->brd_id = SBE_BOARD_ID (PCI_VENDOR_ID_SBE, PCI_DEVICE_ID_WANPMC_C1T3);
break;
--
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/