All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Meiring <johanmeiring@gmail.com>
To: gregkh@suse.de, greg@kroah.com, johanmeiring@gmail.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/6] Staging: wlan-ng: fix coding style issues in prism2mib.c
Date: Sat,  6 Nov 2010 18:23:27 +0200	[thread overview]
Message-ID: <1289060607-13840-1-git-send-email-johanmeiring@gmail.com> (raw)

This is a patch to the prism2mib.c file that fixes various coding style issues that were found by the checkpatch.pl tool

Signed-off-by: Johan Meiring <johanmeiring@gmail.com>
---
 drivers/staging/wlan-ng/prism2mib.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/wlan-ng/prism2mib.c b/drivers/staging/wlan-ng/prism2mib.c
index d3a06fa..c1276fd 100644
--- a/drivers/staging/wlan-ng/prism2mib.c
+++ b/drivers/staging/wlan-ng/prism2mib.c
@@ -136,7 +136,8 @@ static int prism2mib_fragmentationthreshold(struct mibrec *mib,
 					    int isget,
 					    wlandevice_t *wlandev,
 					    hfa384x_t *hw,
-					    struct p80211msg_dot11req_mibset *msg,
+					    struct p80211msg_dot11req_mibset
+						*msg,
 					    void *data);
 
 static int prism2mib_priv(struct mibrec *mib,
@@ -664,7 +665,8 @@ static int prism2mib_fragmentationthreshold(struct mibrec *mib,
 					    int isget,
 					    wlandevice_t *wlandev,
 					    hfa384x_t *hw,
-					    struct p80211msg_dot11req_mibset *msg,
+					    struct p80211msg_dot11req_mibset
+						*msg,
 					    void *data)
 {
 	int result;
-- 
1.7.1


             reply	other threads:[~2010-11-06 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06 16:23 Johan Meiring [this message]
2010-11-10  0:36 ` [PATCH 4/6] Staging: wlan-ng: fix coding style issues in prism2mib.c 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=1289060607-13840-1-git-send-email-johanmeiring@gmail.com \
    --to=johanmeiring@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --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 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.