linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Jan Glauber <jan.glauber@caviumnetworks.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	David Daney <ddaney@caviumnetworks.com>
Subject: Re: [PATCH v2 01/10] i2c-octeon: Cleanup i2c-octeon driver
Date: Sun, 6 Mar 2016 15:35:22 +0100	[thread overview]
Message-ID: <20160306143522.GA5376@katana> (raw)
In-Reply-To: <20160306130038.GC4736@hardcore>

[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]


> Fixed. Strange that checkpatch.pl -f (use on file) does not report these
> errors though.

Huh, indeed.

> > >  struct octeon_i2c {
> > > -	wait_queue_head_t queue;
> > > -	struct i2c_adapter adap;
> > > -	int irq;
> > > -	u32 twsi_freq;
> > > -	int sys_freq;
> > > -	resource_size_t twsi_phys;
> > > -	void __iomem *twsi_base;
> > > -	resource_size_t regsize;
> > > -	struct device *dev;
> > > +	wait_queue_head_t	queue;
> > > +	struct i2c_adapter	adap;
> > > +	int			irq;
> > > +	u32			twsi_freq;
> > > +	int			sys_freq;
> > > +	void __iomem		*twsi_base;
> > > +	struct device		*dev;
> > 
> > NAK. structs change often, and then one needs to fix the whole
> > indentation. One space is enough here.
> 
> Not sure I understand your argument. I find this form more readable
> but I can change that to one space.

a) it spoils git history and makes harder to find out which patch
   added which member of the struct
b) patches get harder to read when the indentation of the whole
   struct changes. New members are not always put at the end.

> > I dunno understand the change of the function name. However, this should
> > be refactored to use the i2c_bus_recovery infrastructure anyhow.
> 
> I'll leave the function name as it is. Would it be possbile to address
> the refactoring in a follow-up patch after this series is finished?

Yes, that makes sense.

> I'll split it into several patches then.

Sounds good. Thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-03-06 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 17:57 [PATCH v2 00/10] i2c-octeon and i2c-thunderx drivers Jan Glauber
2016-03-04 17:57 ` [PATCH v2 01/10] i2c-octeon: Cleanup i2c-octeon driver Jan Glauber
2016-03-05 18:47   ` Wolfram Sang
2016-03-06 13:00     ` Jan Glauber
2016-03-06 14:35       ` Wolfram Sang [this message]
2016-03-04 17:57 ` [PATCH v2 02/10] i2c-octeon: Support I2C_M_RECV_LEN Jan Glauber
2016-03-04 17:57 ` [PATCH v2 03/10] i2c-octeon: Enable high-level controller and improve on bus contention Jan Glauber
2016-03-04 17:57 ` [PATCH v2 04/10] dt-bindings: i2c: add Octeon cn78xx TWSI Jan Glauber
2016-03-04 17:57 ` [PATCH v2 05/10] i2c-octeon: Add support for cn78XX chips Jan Glauber
2016-03-04 17:57 ` [PATCH v2 06/10] i2c-octeon: Flush TWSI writes with readback Jan Glauber
2016-03-04 17:57 ` [PATCH v2 07/10] i2c-octeon: Faster operation when IFLG signals late Jan Glauber
2016-03-04 17:57 ` [PATCH v2 08/10] i2c-octeon: Add workaround for chips with broken irqs Jan Glauber
2016-03-04 17:57 ` [PATCH v2 09/10] i2c: split i2c-octeon driver and add ThunderX support Jan Glauber
2016-03-04 17:57 ` [PATCH v2 10/10] i2c: thunderx: add smbus support Jan Glauber

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=20160306143522.GA5376@katana \
    --to=wsa@the-dreams.de \
    --cc=ddaney@caviumnetworks.com \
    --cc=jan.glauber@caviumnetworks.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@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).