linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Mitchell Tasman <tasman@leaflabs.com>
Cc: Vaibhav Hiremath <hvaibhav.linux@gmail.com>,
	Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, greybus-dev@lists.linaro.org,
	linux-kernel@vger.kernel.org
Subject: Re: [greybus-dev] [PATCH v2] staging: greybus: arche: wrap over-length lines
Date: Mon, 10 Jul 2017 10:16:32 +0530	[thread overview]
Message-ID: <20170710044632.GD2928@vireshk-i7> (raw)
In-Reply-To: <20170710002506.15036-1-tasman@leaflabs.com>

Hi Mitchell,

On 09-07-17, 20:25, Mitchell Tasman wrote:
> Adjust formatting of various statements to keep line length within
> the 80 column limit preferred by the Linux kernel coding style.

We try to follow that most of the time, but the end result should be easily
readable.  If it isn't, then we just ignore the rule.

> Signed-off-by: Mitchell Tasman <tasman@leaflabs.com>
> ---
> Changes in v2: Add back a missing space in a comment
> 
>  drivers/staging/greybus/arche-platform.c | 29 +++++++++++++++++++----------
>  1 file changed, 19 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/staging/greybus/arche-platform.c b/drivers/staging/greybus/arche-platform.c
> index eced2d2..eedd239 100644
> --- a/drivers/staging/greybus/arche-platform.c
> +++ b/drivers/staging/greybus/arche-platform.c
> @@ -172,15 +172,21 @@ static irqreturn_t arche_platform_wd_irq(int irq, void *devid)
>  		if (arche_pdata->wake_detect_state == WD_STATE_BOOT_INIT) {
>  			if (time_before(jiffies,
>  					arche_pdata->wake_detect_start +
> -					msecs_to_jiffies(WD_COLDBOOT_PULSE_WIDTH_MS))) {
> -				arche_platform_set_wake_detect_state(arche_pdata,
> -								     WD_STATE_IDLE);
> +					msecs_to_jiffies(
> +						WD_COLDBOOT_PULSE_WIDTH_MS))) {
> +				arche_platform_set_wake_detect_state(

We don't break the lines like this in kernel to satisfy the 80 column width
rule. Surely, some places would have similar code, but in general this isn't
recommended. And that's why we never bothered about 80 column rule in this and
below cases.

> +								arche_pdata,
> +								WD_STATE_IDLE);
>  			} else {
> -				/* Check we are not in middle of irq thread already */
> +				/*
> +				 * Check we are not in middle of irq thread
> +				 * already
> +				 */

Yes, such changes would be fine.

>  				if (arche_pdata->wake_detect_state !=
>  						WD_STATE_COLDBOOT_START) {
> -					arche_platform_set_wake_detect_state(arche_pdata,
> -									     WD_STATE_COLDBOOT_TRIG);
> +					arche_platform_set_wake_detect_state(

Not this.

> +							arche_pdata,
> +							WD_STATE_COLDBOOT_TRIG);
>  					spin_unlock_irqrestore(
>  						&arche_pdata->wake_lock,
>  						flags);
> @@ -199,8 +205,9 @@ static irqreturn_t arche_platform_wd_irq(int irq, void *devid)
>  			 * beyond 30msec, then it is coldboot else fallback
>  			 * to standby boot.
>  			 */
> -			arche_platform_set_wake_detect_state(arche_pdata,
> -							     WD_STATE_BOOT_INIT);
> +			arche_platform_set_wake_detect_state(

Not this.

> +							arche_pdata,
> +							WD_STATE_BOOT_INIT);
>  		}
>  	}
>  
> @@ -657,12 +664,14 @@ static SIMPLE_DEV_PM_OPS(arche_platform_pm_ops,
>  			arche_platform_resume);
>  
>  static const struct of_device_id arche_platform_of_match[] = {
> -	{ .compatible = "google,arche-platform", }, /* Use PID/VID of SVC device */
> +	/* Use PID/VID of SVC device */
> +	{ .compatible = "google,arche-platform", },

This would be fine though.

>  	{ },
>  };
>  
>  static const struct of_device_id arche_combined_id[] = {
> -	{ .compatible = "google,arche-platform", }, /* Use PID/VID of SVC device */
> +	/* Use PID/VID of SVC device */
> +	{ .compatible = "google,arche-platform", },
>  	{ .compatible = "usbffff,2", },
>  	{ },
>  };

-- 
viresh

  reply	other threads:[~2017-07-10  4:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 21:28 [PATCH] staging: greybus: arche: wrap over-length lines Mitchell Tasman
2017-07-10  0:25 ` [PATCH v2] " Mitchell Tasman
2017-07-10  4:46   ` Viresh Kumar [this message]
2017-07-10  9:30     ` [greybus-dev] " Frans Klaver
2017-07-10  9:31       ` Viresh Kumar
2017-07-11  5:24         ` Joe Perches
2017-07-11  3:14     ` [PATCH v3] " Mitchell Tasman
2017-07-11  3:22       ` [greybus-dev] " Viresh Kumar

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=20170710044632.GD2928@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=hvaibhav.linux@gmail.com \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tasman@leaflabs.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;
as well as URLs for NNTP newsgroup(s).