From: Joe Perches <joe@perches.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Daniel Vetter <daniel@ffwll.ch>,
Christophe LEROY <christophe.leroy@c-s.fr>
Cc: daniel.lezcano@linaro.org, heiko@sntech.de,
narmstrong@baylibre.com, airlied@linux.ie,
benh@kernel.crashing.org, linus.walleij@linaro.org,
Alexey.Brodkin@synopsys.com, will.deacon@arm.com,
fbarrat@linux.vnet.ibm.com,
kernel list <linux-kernel@vger.kernel.org>,
paulus@ozlabs.org, yamada.masahiro@socionext.com,
mhocko@suse.com, viresh.kumar@linaro.org,
Pavel Machek <pavel@ucw.cz>,
hpa@zytor.com, JinHuiEric.Huang@amd.com, Rex.Zhu@amd.com,
elfring@users.sourceforge.net, scott.bauer@intel.com,
David1.Zhou@amd.com, architt@codeaurora.org,
linux-arm-kernel@lists.infradead.org, joro@8bytes.org,
x86@kernel.org, Wenjing.Liu@amd.com, linux@armlinux.org.uk,
amd-gfx@lists.freedesktop.org, Ding.Wang@amd.com, aik@ozlabs.ru,
wens@csie.org, mingo@redhat.com, vbabka@suse.cz,
catalin.marinas@arm.com, airlied@redhat.com, ruscur@russell.cc,
shli@kernel.org, dan.carpenter@oracle.com, andresx7@
Subject: Re: [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 at 17:19 +1100, Michael Ellerman wrote:
> Daniel Vetter <daniel@ffwll.ch> writes:
> > On Sun, Feb 18, 2018 at 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@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: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180217211955.GE9640@amd>
[not found] ` <187435d4-5017-edb5-9b6a-b433a148bfcc@c-s.fr>
2018-02-19 15:41 ` [PATCH] fix double ;;s in code Daniel Vetter
[not found] ` <20180219193312.GA3709@amd>
2018-02-20 1:25 ` Rob Clark
[not found] ` <87o9kkcck3.fsf@intel.com>
2018-02-20 16:34 ` Alex Deucher
2018-02-20 23:47 ` Andrew Morton
[not found] ` <20180219154135.GV22199-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
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=Alexey.Brodkin@synopsys.com \
--cc=David1.Zhou@amd.com \
--cc=Ding.Wang@amd.com \
--cc=JinHuiEric.Huang@amd.com \
--cc=Rex.Zhu@amd.com \
--cc=Wenjing.Liu@amd.com \
--cc=aik@ozlabs.ru \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=architt@codeaurora.org \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@c-s.fr \
--cc=dan.carpenter@oracle.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@ffwll.ch \
--cc=elfring@users.sourceforge.net \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=heiko@sntech.de \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=narmstrong@baylibre.com \
--cc=paulus@ozlabs.org \
--cc=pavel@ucw.cz \
--cc=ruscur@russell.cc \
--cc=scott.bauer@intel.com \
--cc=shli@kernel.org \
--cc=vbabka@suse.cz \
--cc=viresh.kumar@linaro.org \
--cc=wens@csie.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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).