From: Shiva Kerdel <shiva@exdev.nl>
To: German.Rivera@freescale.com
Cc: stuart.yoder@nxp.com, gregkh@linuxfoundation.org,
german.rivera@nxp.com, itai.katz@nxp.com, treding@nvidia.com,
bharat.bhushan@nxp.com, nipun.gupta@nxp.com,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
Shiva Kerdel <shiva@exdev.nl>
Subject: [PATCH 4/6] Staging: fsl-mc: bus: dpmcp: Kernel type 'u64' preferred over 'uint64_t'
Date: Mon, 7 Nov 2016 13:01:23 +0100 [thread overview]
Message-ID: <20161107120125.4663-4-shiva@exdev.nl> (raw)
In-Reply-To: <20161107120125.4663-1-shiva@exdev.nl>
Follow the kernel type preferrences of using 'u64' over 'uint64_t'.
Signed-off-by: Shiva Kerdel <shiva@exdev.nl>
---
drivers/staging/fsl-mc/bus/dpmcp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/fsl-mc/bus/dpmcp.h b/drivers/staging/fsl-mc/bus/dpmcp.h
index 854621a..c4e5d05 100644
--- a/drivers/staging/fsl-mc/bus/dpmcp.h
+++ b/drivers/staging/fsl-mc/bus/dpmcp.h
@@ -85,7 +85,7 @@ int dpmcp_reset(struct fsl_mc_io *mc_io,
* @irq_num: A user defined number associated with this IRQ
*/
struct dpmcp_irq_cfg {
- uint64_t paddr;
+ u64 paddr;
u32 val;
int irq_num;
};
--
2.10.2
next prev parent reply other threads:[~2016-11-07 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 12:01 [PATCH 1/6] Staging: fsl-mc: bus: dpmcp: Kernel type 'u32' preferred over 'uint32_t' Shiva Kerdel
2016-11-07 12:01 ` [PATCH 2/6] Staging: fsl-mc: bus: dpmcp: Kernel type 'u16' preferred over 'uint16_t' Shiva Kerdel
2016-11-07 12:01 ` [PATCH 3/6] Staging: fsl-mc: bus: dpmcp: Kernel type 'u8' preferred over 'uint8_t' Shiva Kerdel
2016-11-07 12:01 ` Shiva Kerdel [this message]
2016-11-07 12:01 ` [PATCH 5/6] Staging: fsl-mc: include: mc: Kernel type 's32' preferred over 'int32_t' Shiva Kerdel
2016-11-07 12:01 ` [PATCH 6/6] Staging: fsl-mc: include: mc-bus: Kernel type 's16' preferred over 'int16_t' Shiva Kerdel
2016-11-07 23:50 ` [PATCH 1/6] Staging: fsl-mc: bus: dpmcp: Kernel type 'u32' preferred over 'uint32_t' Stuart Yoder
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=20161107120125.4663-4-shiva@exdev.nl \
--to=shiva@exdev.nl \
--cc=German.Rivera@freescale.com \
--cc=bharat.bhushan@nxp.com \
--cc=devel@driverdev.osuosl.org \
--cc=german.rivera@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=itai.katz@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nipun.gupta@nxp.com \
--cc=stuart.yoder@nxp.com \
--cc=treding@nvidia.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
Powered by JetHome