lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAH7P7Nhz2FpBct4afvAXU2Zgi-yA4TkJj7CtYMaW7pXr6weZig@mail.gmail.com> Date: Tue, 18 Dec 2012 11:05:33 +0100 From: Laurent Navet <laurent.navet@...il.com> To: Jean Delvare <khali@...ux-fr.org> Cc: w.sang@...gutronix.de, ben-linux@...ff.org, linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] driver i2c-nforce2: fix pointer CodingStyle issues Hi guys, > This is correct, however there are several other checkpatch errors and > warnings in this file and I would appreciate if you could fix them as > well. I'm not asking that you fix them all, but please consider fixing > the following: > > WARNING: space prohibited between function name and open parenthesis '(' > #63: FILE: i2c/busses/i2c-nforce2.c:63: > +MODULE_AUTHOR ("Hans-Frieder Vogt <hfvogt@....net>"); > > WARNING: suspect code indent for conditional statements (24, 33) > #226: FILE: i2c/busses/i2c-nforce2.c:226: > + if (read_write == I2C_SMBUS_WRITE) { > + outb_p(data->word, NVIDIA_SMB_DATA); > > WARNING: line over 80 characters > #275: FILE: i2c/busses/i2c-nforce2.c:275: > + data->word = inb_p(NVIDIA_SMB_DATA) | (inb_p(NVIDIA_SMB_DATA+1) << 8); > > WARNING: quoted string split across lines > #282: FILE: i2c/busses/i2c-nforce2.c:282: > + dev_err(&adap->dev, "Transaction failed " > + "(received block size: 0x%02x)\n", > > WARNING: space prohibited between function name and open parenthesis '(' > #330: FILE: i2c/busses/i2c-nforce2.c:330: > +MODULE_DEVICE_TABLE (pci, nforce2_ids); > > WARNING: line over 80 characters > #380: FILE: i2c/busses/i2c-nforce2.c:380: > + dev_info(&smbus->adapter.dev, "nForce2 SMBus adapter at %#x\n", > smbus->base); > > ERROR: space required before the open parenthesis '(' > #395: FILE: i2c/busses/i2c-nforce2.c:395: > + switch(dev->device) { > > These are simple coding style issues, very easy to fix. i have planned fixing these too, do you prefer one patch fixing all or multiple patches (one per error/warning type )? regards, Laurent. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists