From: joe@perches.com (Joe Perches)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] fix double ;;s in code
Date: Tue, 20 Feb 2018 08:41:10 -0800 [thread overview]
Message-ID: <1519144870.4326.7.camel@perches.com> (raw)
In-Reply-To: <87vaesrxn0.fsf@concordia.ellerman.id.au>
On Tue, 2018-02-20@17:19 +1100, Michael Ellerman wrote:
> Daniel Vetter <daniel at ffwll.ch> writes:
> > On Sun, Feb 18, 2018@11:00:56AM +0100, Christophe LEROY wrote:
> > > Le 17/02/2018 ? 22:19, Pavel Machek a ?crit :
> > > >
> > > > Fix double ;;'s in code.
> > > >
> > > > Signed-off-by: Pavel Machek <pavel at ucw.cz>
> > >
> > > A summary of the files modified on top of the patch would help understand
> > > the impact.
> > >
> > > A maybe there should be one patch by area, eg one for each arch specific
> > > modif and one for drivers/ and one for block/ ?
> >
> > Yeah, pls split this into one patch per area, with a suitable patch
> > subject prefix. Look at git log of each file to get a feeling for what's
> > the standard in each area.
>
> This part is actually pretty annoying.
>
> I hacked up a script (below) which seems to do a reasonable job in most
> cases.
Here was another suggestion from awhile ago
https://lkml.org/lkml/2010/11/16/245
next prev parent reply other threads:[~2018-02-20 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 21:19 [PATCH] fix double ;;s in code Pavel Machek
2018-02-18 10:00 ` Christophe LEROY
2018-02-19 15:41 ` Daniel Vetter
2018-02-19 19:33 ` Pavel Machek
2018-02-20 1:25 ` Rob Clark
2018-02-20 8:03 ` Jani Nikula
2018-02-20 16:34 ` Alex Deucher
2018-02-20 23:47 ` Andrew Morton
2018-02-20 6:19 ` Michael Ellerman
2018-02-20 16:41 ` Joe Perches [this message]
2018-02-22 9:09 ` Shawn Guo
2018-02-24 8:52 ` Pavel Machek
2018-02-24 8:56 ` Shawn Guo
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=1519144870.4326.7.camel@perches.com \
--to=joe@perches.com \
--cc=linux-snps-arc@lists.infradead.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