From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/3 v3] ARM: shmobile: r8a7778: add I2C support
Date: Sun, 02 Jun 2013 19:41:00 +0000 [thread overview]
Message-ID: <51AB9FCC.3090909@cogentembedded.com> (raw)
In-Reply-To: <8738t7ag43.wl%kuninori.morimoto.gx@renesas.com>
Hello.
On 05/28/2013 08:22 AM, Kuninori Morimoto wrote:
> Add a platform device for the r8a7778 I2C.
>
> Signed-off-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
[...]
> diff --git a/arch/arm/mach-shmobile/setup-r8a7778.c b/arch/arm/mach-shmobile/setup-r8a7778.c
> index 9191acc..eaa6b06 100644
> --- a/arch/arm/mach-shmobile/setup-r8a7778.c
> +++ b/arch/arm/mach-shmobile/setup-r8a7778.c
> @@ -173,6 +173,31 @@ void __init r8a7778_sdhi_init(int id,
[...]
> +void __init r8a7778_add_i2c_device(int id)
> +{
> + BUG_ON(id < 0 || id > 3);
> +
> + platform_device_register_simple(
> + "i2c-rcar", id,
> + i2c_resources + (2 * id), 2);
I don't understand why are you wrapping the lines so early here
(this remark
relates to all the series). This is not a standard way to indent the
function call
continuation lines, normally you should align them to the next character
after (.
WBR, Sergei
next prev parent reply other threads:[~2013-06-02 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 4:22 [PATCH 1/3 v3] ARM: shmobile: r8a7778: add I2C support Kuninori Morimoto
2013-06-02 17:16 ` Sergei Shtylyov
2013-06-02 19:41 ` Sergei Shtylyov [this message]
2013-06-04 2:28 ` Simon Horman
2013-06-04 3:22 ` Kuninori Morimoto
2013-06-04 7:53 ` Simon Horman
2013-08-02 1:02 ` [PATCH 1/3 v3] ARM: shmobile: r8a7778: add usb phy power control function Kuninori Morimoto
2013-08-02 12:17 ` Sergei Shtylyov
2013-08-02 13:18 ` Ben Dooks
2013-08-04 23:53 ` Kuninori Morimoto
2013-08-05 0:28 ` Kuninori Morimoto
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=51AB9FCC.3090909@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).