linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Matheina <scott@matheina.com>
To: Joe Perches <joe@perches.com>, gregkh@linuxfoundation.org
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] indention and space fixes to align with linux style
Date: Wed, 21 Dec 2016 19:02:22 -0600	[thread overview]
Message-ID: <518f5c19-26f3-9896-64c8-ec2a2b592c5c@matheina.com> (raw)
In-Reply-To: <1482290625.1984.33.camel@perches.com>



On 12/20/2016 09:23 PM, Joe Perches wrote:
> On Tue, 2016-12-20 at 20:58 -0600, Scott Matheina wrote:
>> Fixed indention and space issues to align the code with the linux style guide.
> []
>> diff --git a/drivers/staging/iio/addac/adt7316.c b/drivers/staging/iio/addac/adt7316.c
> []
>> @@ -176,16 +176,16 @@
>>    */
>>
>>   struct adt7316_chip_info {
>> -	struct adt7316_bus	bus;
>> -	u16			ldac_pin;
>> -	u16			int_mask;	/* 0x2f */
>> -	u8			config1;
>> -	u8			config2;
>> -	u8			config3;
>> -	u8			dac_config;	/* DAC config */
>> -	u8			ldac_config;	/* LDAC config */
>> -	u8			dac_bits;	/* 8, 10, 12 */
>> -	u8			id;		/* chip id */
>> +	struct adt7316_bus bus;
>> +	u16 ldac_pin;
>> +	u16 int_mask;		/* 0x2f */
>> +	u8 config1;
>> +	u8 config2;
>> +	u8 config3;
>> +	u8 dac_config;		/* DAC config */
>> +	u8 ldac_config;		/* LDAC config */
>> +	u8 dac_bits;		/* 8, 10, 12 */
>> +	u8 id;			/* chip id */
>>   };
> Hello Scott.
>
> I believe you're relatively new at this
> patch submission stuff.
>
> The style above is fine and doesn't need
> to be changed.  It is not in CodingStyle
> as preferred one way or the other.
>
>>   /*
>> @@ -212,13 +212,12 @@ struct adt7316_chip_info {
>>    */
>>
>>   struct adt7316_limit_regs {
>> -	u16	data_high;
>> -	u16	data_low;
>> +	u16 data_high;
>> +	u16 data_low;
>>   };
>>
>>   static ssize_t adt7316_show_enabled(struct device *dev,
>> -		struct device_attribute *attr,
>> -		char *buf)
>> +				    struct device_attribute *attr, char *buf)
> This one isn't either but it is a very common
> style in net/, drivers/net, and drivers/staging
> though.
>
The problem I'm running into is when I use Lindent, it automatically 
makes the
change above, so I can't use that tool for the file. Even when I correct 
the changes
in the file git diff still shows the non-change, so I'm just trying to 
figure out how
to use the given tools without having these issues. I'm going to just go 
manual with
my future changes is suppose.

  parent reply	other threads:[~2016-12-22  1:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  2:58 [PATCH] indention and space fixes to align with linux style Scott Matheina
2016-12-21  3:23 ` Joe Perches
2016-12-21  3:41   ` Scott Matheina
2016-12-22  1:02   ` Scott Matheina [this message]
2016-12-22  1:10     ` 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=518f5c19-26f3-9896-64c8-ec2a2b592c5c@matheina.com \
    --to=scott@matheina.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=joe@perches.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).