From: Stephen Boyd <sboyd@codeaurora.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: York Sun <yorksun@freescale.com>,
linux-clk@vger.kernel.org,
Mike Turquette <mturquette@baylibre.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Andrey Filippov <andrey@elphel.com>,
Paul Bolle <pebolle@tiscali.nl>
Subject: Re: [Patch v5] driver/clk/clk-si5338: Add common clock framework driver for si5338
Date: Thu, 1 Oct 2015 15:20:55 -0700 [thread overview]
Message-ID: <20151001222055.GN19319@codeaurora.org> (raw)
In-Reply-To: <5604A9F0.2050600@roeck-us.net>
On 09/24, Guenter Roeck wrote:
> On 09/24/2015 05:46 PM, York Sun wrote:
> >+ /* may have some garbage in high bits,
> >+ * will be cut of by mask
> >+ */
>
> Does the clock subsystem use network subsystem style multiline comments ?
No. We follow the traditional multi-line commenting style as in
Documentation/CodingStyle.
> >+ return ret;
> >+ }
> >+
> >+ /* Check if si5338 exists */
> >+ if ((n & REG5338_DEV_CONFIG2_MASK) != REG5338_DEV_CONFIG2_VAL) {
> >+ dev_err(&client->dev,
> >+ "Chip returned unexpected value from reg %d: %d, expected %d. It is not %s\n",
>
> 0x%x for register values ?
Or %#x
>
> >+ REG5338_DEV_CONFIG2, n, REG5338_DEV_CONFIG2_VAL,
> >+ id->name);
> >+ return -EIO;
> >+ }
> >+
> >+ dev_info(&client->dev, "Chip %s is found\n", id->name);
>
> I personally dislike that noise.
>
Me too.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-10-01 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 0:46 [Patch v5] driver/clk/clk-si5338: Add common clock framework driver for si5338 York Sun
2015-09-25 1:57 ` Guenter Roeck
2015-09-25 15:04 ` York Sun
2015-10-01 22:20 ` Stephen Boyd [this message]
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=20151001222055.GN19319@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=andrey@elphel.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mturquette@baylibre.com \
--cc=pebolle@tiscali.nl \
--cc=sebastian.hesselbarth@gmail.com \
--cc=yorksun@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 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.