From: Jean Delvare <khali@linux-fr.org>
To: Laurent Navet <laurent.navet@gmail.com>
Cc: w.sang@pengutronix.de, ben-linux@fluff.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: i2c-nforce2: fix coding style issues
Date: Thu, 10 Jan 2013 09:32:55 +0100 [thread overview]
Message-ID: <20130110093255.5353fb31@endymion.delvare> (raw)
In-Reply-To: <1357764624-32134-1-git-send-email-laurent.navet@gmail.com>
Hi Laurent,
Thanks for the updated patch.
On Wed, 9 Jan 2013 21:50:24 +0100, Laurent Navet wrote:
> avoid these checkpatch.pl issues :
> - ERROR: "foo * bar" should be "foo *bar"
> - ERROR: switch and case should be at the same indent
> - ERROR: "(foo*)" should be "(foo *)"
> - ERROR: do not use assignment in if condition
> - ERROR: space required before the open parenthesis '('
> - WARNING: suspect code indent for conditional statements
> - WARNING: quoted string split across lines
> - WARNING: space prohibited between function name and open parenthesis '('
Unfortunately your patch also add one new checkpatch.pl warning:
WARNING: line over 80 characters
#245: FILE: drivers/i2c/busses/i2c-nforce2.c:272:
+ data->word = inb_p(NVIDIA_SMB_DATA) | (inb_p(NVIDIA_SMB_DATA + 1) << 8);
Please fix.
>
> Signed-off-by: Laurent Navet <laurent.navet@gmail.com>
> ---
> drivers/i2c/busses/i2c-nforce2.c | 153 +++++++++++++++++++-------------------
> 1 file changed, 76 insertions(+), 77 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-nforce2.c b/drivers/i2c/busses/i2c-nforce2.c
> index 392303b..90357a2 100644
> --- a/drivers/i2c/busses/i2c-nforce2.c
> +++ b/drivers/i2c/busses/i2c-nforce2.c
> (...)
> @@ -327,10 +324,10 @@ static DEFINE_PCI_DEVICE_TABLE(nforce2_ids) = {
> { 0 }
> };
>
> -MODULE_DEVICE_TABLE (pci, nforce2_ids);
> +MODULE_DEVICE_TABLE(pci, nforce2_ids);
>
>
> -static int __devinit nforce2_probe_smb (struct pci_dev *dev, int bar,
> +static int __devinit nforce2_probe_smb(struct pci_dev *dev, int bar,
> int alt_reg, struct nforce2_smbus *smbus, const char *name)
> {
> int error;
As mentioned previously, __devinit has been dropped meanwhile, so this
change doesn't apply cleanly. Please rebase your patch on top of kernel
3.8-rc3 (or Wolfram's i2c tree) so that Wolfram can apply it.
All the rest looks very good now, thanks for the good work.
--
Jean Delvare
next prev parent reply other threads:[~2013-01-10 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 20:50 Laurent Navet
2013-01-10 8:32 ` Jean Delvare [this message]
2013-01-10 8:52 ` Laurent Navet
2013-01-10 9:21 ` Jean Delvare
2013-01-10 9:40 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 14:07 Laurent Navet
2013-01-10 16:34 ` Jean Delvare
2013-01-24 7:27 ` Wolfram Sang
2012-12-19 21:06 Laurent Navet
2012-12-21 10:04 ` Jean Delvare
2012-12-21 14:15 ` Laurent Navet
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=20130110093255.5353fb31@endymion.delvare \
--to=khali@linux-fr.org \
--cc=ben-linux@fluff.org \
--cc=laurent.navet@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®