Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Marc St-Jean <Marc_St-Jean@pmc-sierra.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org,
	Brian Oostenbrink <Brian_Oostenbrink@pmc-sierra.com>,
	Dan Doucette <Dan_Doucette@pmc-sierra.com>
Subject: Re: [PATCH 1/12] mips: PMC MSP71xx core platform
Date: Wed, 20 Jun 2007 09:58:34 -0700	[thread overview]
Message-ID: <46795CBA.7090408@pmc-sierra.com> (raw)



Ralf Baechle wrote:
> On Thu, Jun 14, 2007 at 03:54:47PM -0600, Marc St-Jean wrote:
> 
>  > Re-posting patch as requested by Ralf. Changes since last post:
>  > -Minor cleanups as recommended by checkpatch.pl.
> 
> Be careful with that script.  Some of it's recommendations are harmful,
> for example when it sees an inclusion of <asm/time.h> it will suggest
> to use <linux/time.h>.  That's all fine because generally the file under
> linux/ will include the asm/ version but there are exception.

I discovered that on some patches, a few had to be reverted but no problem.

> But it's great that you discovered it already, it saves me the for both
> sides annoying part of dealing out tons of trivialities, first such as
> formatting trivialities.  One thing checkpatch.pl doesn't yet complain
> about is trailing whitespace such as in the first of the patches you
> sent:
> 
> Warning: trailing whitespace in line 106 of 
> arch/mips/pmc-sierra/msp71xx/msp_usb.c
> Warning: trailing whitespace in line 12 of 
> arch/mips/pmc-sierra/msp71xx/msp_irq_slp.c
> Warning: trailing whitespace in lines 43,53,63,79 of 
> arch/mips/pmc-sierra/msp71xx/msp_time.c
> Warning: trailing whitespace in lines 49,59,62,68,78,84 of 
> arch/mips/pmc-sierra/msp71xx/msp_irq.c
> Warning: trailing whitespace in line 84 of 
> arch/mips/pmc-sierra/msp71xx/msp_irq_cic.c
> Warning: trailing whitespace in line 157 of 
> arch/mips/pmc-sierra/msp71xx/msp_hwbutton.c
> Warning: trailing whitespace in lines 154,307,537,548,558 of 
> arch/mips/pmc-sierra/msp71xx/msp_prom.c
> Warning: trailing whitespace in lines 66,229,238,252 of 
> arch/mips/pmc-sierra/msp71xx/msp_setup.c
> 
> No need to resend the patch, I can strip that of trivially

Hmmm, I see. That's odd since it catches most trailing whitespace. I'll
email the maintainer if you haven't already. I've reported two other
issues to him before and he fixed the script in a day!

Marc

             reply	other threads:[~2007-06-20 16:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 16:58 Marc St-Jean [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-29 17:18 [PATCH 1/12] mips: PMC MSP71xx core platform Marc St-Jean
2007-06-29  1:05 Marc St-Jean
2007-06-29  1:33 ` Yoichi Yuasa
2007-06-22 17:33 Marc St-Jean
2007-06-21 19:18 Marc St-Jean
2007-06-14 21:54 Marc St-Jean
2007-06-20  8:27 ` Ralf Baechle
2007-06-21 16:55 ` Ralf Baechle
2007-04-27 19:59 Marc St-Jean
2007-03-26 21:53 Marc St-Jean
2007-03-19 17:58 Marc St-Jean
2007-03-20  1:06 ` Atsushi Nemoto
2007-03-17  0:04 Marc St-Jean
2007-03-16 21:32 Marc St-Jean
2007-03-16 23:24 ` Ralf Baechle
2007-03-17 13:30 ` Atsushi Nemoto

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=46795CBA.7090408@pmc-sierra.com \
    --to=marc_st-jean@pmc-sierra.com \
    --cc=Brian_Oostenbrink@pmc-sierra.com \
    --cc=Dan_Doucette@pmc-sierra.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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