public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nayeemahmed Badebade <itachi.opsrc@gmail.com>
To: gregkh@linuxfoundation.org
Cc: German.Rivera@freescale.com, stuart.yoder@freescale.com,
	agraf@suse.de, hgujulan@visteon.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH] Staging: fsl-mc/bus: mc-bus.c: Fixed coding style issues
Date: Fri,  4 Sep 2015 22:30:33 +0530	[thread overview]
Message-ID: <1441386033-2900-1-git-send-email-itachi.opsrc@gmail.com> (raw)
In-Reply-To: <20150903164834.GD31709@kroah.com>

Fixed coding style issues where kernel types u16,u64,u32 should
be preferred over uint16_t,uint64_t,uint32_t

Signed-off-by: Nayeemahmed Badebade <itachi.opsrc@gmail.com>
---
 drivers/staging/fsl-mc/bus/mc-bus.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/fsl-mc/bus/mc-bus.c b/drivers/staging/fsl-mc/bus/mc-bus.c
index 766a659..b3a60a0 100644
--- a/drivers/staging/fsl-mc/bus/mc-bus.c
+++ b/drivers/staging/fsl-mc/bus/mc-bus.c
@@ -209,7 +209,7 @@ EXPORT_SYMBOL_GPL(fsl_mc_driver_unregister);
 static int get_dprc_icid(struct fsl_mc_io *mc_io,
 			 int container_id, uint16_t *icid)
 {
-	uint16_t dprc_handle;
+	u16 dprc_handle;
 	struct dprc_attributes attr;
 	int error;
 
@@ -234,7 +234,7 @@ common_cleanup:
 	return error;
 }
 
-static int translate_mc_addr(uint64_t mc_addr, phys_addr_t *phys_addr)
+static int translate_mc_addr(u64 mc_addr, phys_addr_t *phys_addr)
 {
 	int i;
 	struct fsl_mc *mc = dev_get_drvdata(fsl_mc_bus_type.dev_root->parent);
@@ -600,7 +600,7 @@ static int fsl_mc_bus_probe(struct platform_device *pdev)
 	struct fsl_mc_io *mc_io = NULL;
 	int container_id;
 	phys_addr_t mc_portal_phys_addr;
-	uint32_t mc_portal_size;
+	u32 mc_portal_size;
 	struct mc_version mc_version;
 	struct resource res;
 
-- 
1.9.1


  reply	other threads:[~2015-09-04 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 17:24 [PATCH] Staging: fsl-mc/bus: mc-bus.c: Fixed coding style issues nayeem
2015-09-03 16:48 ` Greg KH
2015-09-04 17:00   ` Nayeemahmed Badebade [this message]
2015-09-04 17:48     ` Jose Rivera
2015-09-04 18:00       ` gregkh
2015-09-04 18:33         ` Joe Perches

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=1441386033-2900-1-git-send-email-itachi.opsrc@gmail.com \
    --to=itachi.opsrc@gmail.com \
    --cc=German.Rivera@freescale.com \
    --cc=agraf@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hgujulan@visteon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuart.yoder@freescale.com \
    /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