mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Schilman <maurito.s@gmail.com>
To: gregkh@suse.de
Cc: u.kleine-koenig@pengutronix.de, eli@siliconsprawl.com,
	michael.tate@wanadoo.fr, arnd@arndb.de,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	ehames@gmail.com, maurito.s@gmail.com, md.bustos90@gmail.com,
	facugaich@gmail.com
Subject: [PATCH] Staging: frontier: fix space and * coding style issues in alphatrack.c
Date: Mon,  1 Nov 2010 18:38:10 -0300	[thread overview]
Message-ID: <1288647490-2088-1-git-send-email-maurito.s@gmail.com> (raw)

 This is a patch to the alphatrack.c file that fixes up a space warning and a
     space after '*' warning found by the checkpatch.pl tool
 Signed-off-by: Mauro Schilman <maurito.s@gmail.com>

---
 drivers/staging/frontier/alphatrack.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/frontier/alphatrack.c b/drivers/staging/frontier/alphatrack.c
index ef7fbf8..2babb03 100644
--- a/drivers/staging/frontier/alphatrack.c
+++ b/drivers/staging/frontier/alphatrack.c
@@ -89,7 +89,7 @@ static int debug = ALPHATRACK_DEBUG;
 
 /* Use our own dbg macro */
 #define dbg_info(dev, format, arg...) do \
-    { if (debug) dev_info(dev , format , ## arg); } while (0)
+	{ if (debug) dev_info(dev , format , ## arg); } while (0)
 
 #define alphatrack_ocmd_info(dev, cmd, format, arg...)
 
@@ -769,7 +769,7 @@ static int usb_alphatrack_probe(struct usb_interface *intf,
 	}
 
 	dev->write_buffer =
-	    kmalloc(sizeof(struct alphatrack_ocmd) * true_size, GFP_KERNEL);
+	    kmalloc(true_size * sizeof(struct alphatrack_ocmd), GFP_KERNEL);
 
 	if (!dev->write_buffer) {
 		dev_err(&intf->dev, "Couldn't allocate write_buffer\n");
-- 
1.7.1


                 reply	other threads:[~2010-11-01 21:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1288647490-2088-1-git-send-email-maurito.s@gmail.com \
    --to=maurito.s@gmail.com \
    --cc=arnd@arndb.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=ehames@gmail.com \
    --cc=eli@siliconsprawl.com \
    --cc=facugaich@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=md.bustos90@gmail.com \
    --cc=michael.tate@wanadoo.fr \
    --cc=u.kleine-koenig@pengutronix.de \
    /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

all inboxes | Powered by JetHome®