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
WARNING: multiple messages have this Message-ID (diff)
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: Pavel Machek <pavel@ucw.cz>,
elfring@users.sourceforge.net,
kernel list <linux-kernel@vger.kernel.org>,
vgupta@synopsys.com, linux@armlinux.org.uk, oleg@redhat.com,
catalin.marinas@arm.com, will.deacon@arm.com, paulus@ozlabs.org,
benh@kernel.crashing.org, ard.biesheuvel@linaro.org,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, scott.bauer@intel.com,
jonathan.derrick@intel.com, axboe@kernel.dk,
daniel.lezcano@linaro.org, maxime.ripard@free-electrons.com,
wens@csie.org, alexander.deucher@amd.com,
christian.koenig@amd.com, David1.Zhou@amd.com, airlied@linux.ie,
robdclark@gmail.com, joro@8bytes.org, shli@kernel.org,
shawnguo@kernel.org, kernel@pengutronix.de,
fabio.estevam@nxp.com, akpm@linux-foundation.org,
Alexey.Brodkin@synopsys.com, mhocko@suse.com, vbabka@suse.cz,
Vladislav.Zakharov@synopsys.com, noamca@mellanox.com,
yamada.masahiro@socionext.com, sboyd@codeaurora.org,
viresh.kumar@linaro.org, linus.walleij@linaro.org,
heiko@sntech.de, aik@ozlabs.ru, ruscur@russell.cc,
david@gibson.dropbear.id.au, fbarrat@linux.vnet.ibm.com,
alistair@popple.id.au, robh@kernel.org, harry.wentland@amd.com,
tony.cheng@amd.com, Wenjing.Liu@amd.com, airlied@redhat.com,
Ding.Wang@amd.com, sylvia.tsai@amd.com, hersenxs.wu@amd.com,
Rex.Zhu@amd.com, JinHuiEric.Huang@amd.com,
dan.carpenter@oracle.com, architt@codeaurora.org,
daniel.vetter@ffwll.ch, narmstrong@baylibre.com,
ville.syrjala@linux.intel.com, jcrouse@codeaurora.org,
aishpant@gmail.com, noralf@tronnes.org, andresx7@gmail.com,
Monk.Liu@amd.com, nicolai.haehnle@amd.com,
Andrey.Grodzovsky@amd.com, linux-snps-arc@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, kvm-ppc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-efi@vger.kernel.org,
linux-block@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org,
iommu@lists.linux-foundation.org, linux-raid@vger.kernel.org
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
WARNING: multiple messages have this Message-ID (diff)
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
WARNING: multiple messages have this Message-ID (diff)
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: Pavel Machek <pavel@ucw.cz>,
elfring@users.sourceforge.net,
kernel list <linux-kernel@vger.kernel.org>,
vgupta@synopsys.com, linux@armlinux.org.uk, oleg@redhat.com,
catalin.marinas@arm.com, will.deacon@arm.com, paulus@ozlabs.org,
benh@kernel.crashing.org, ard.biesheuvel@linaro.org,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, scott.bauer@intel.com,
jonathan.derrick@intel.com, axboe@kernel.dk,
daniel.lezcano@linaro.org, maxime.ripard@free-electrons.com,
wens@csie.org, alexander.deucher@amd.com,
christian.koenig@amd.com, David1.Zhou@amd.com, airlied@linux.ie,
robdclark@gmail.com, joro@8bytes.org, shli@kernel.org,
shawnguo@kernel.org, kernel@pengutronix.de,
fabio.estevam@nxp.com, akpm@linux-foundation.org,
Alexey.Brodkin@synopsys.com, mhocko@suse.com, vbabka@suse.cz,
Vladislav.Zakharov@synopsys.com, noamca@mellanox.com,
yamada.masahiro@socionext.com, sboyd@codeaurora.org,
viresh.kumar@linaro.org, linus.walleij@linaro.org,
heiko@sntech.de, aik@ozlabs.ru, ruscur@russell.cc,
david@gibson.dropbear.id.au, fbarrat@linux.vnet.ibm.com,
alistair@popple.id.au, robh@kernel.org, harry.wentland@amd.com,
tony.cheng@amd.com, Wenjing.Liu@amd.com, airlied@redhat.com,
Ding.Wang@amd.com, sylvia.tsai@amd.com, hersenxs.wu@amd.com,
Rex.Zhu@amd.com, JinHuiEric.Huang@amd.com,
dan.carpenter@oracle.com, architt@codeaurora.org,
daniel.vetter@ffwll.ch, narmstrong@baylibre.com,
ville.syrjala@linux.intel.com, jcrouse@codeaurora.org,
aishpant@gmail.com, noralf@tronnes.org, andresx7@gmail.com,
Monk.Liu@amd.com, nicolai.haehnle@amd.com,
Andrey.Grodzovsky@amd.com, linux-snps-arc@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, kvm-ppc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-efi@vger.kernel.org,
linux-block@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org,
iommu@lists.linux-foundation.org, linux-raid@vger.kernel.org
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: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 21:19 [PATCH] fix double ;;s in code Pavel Machek
2018-02-17 21:19 ` Pavel Machek
2018-02-17 21:19 ` Pavel Machek
2018-02-18 10:00 ` Christophe LEROY
2018-02-18 10:00 ` Christophe LEROY
2018-02-18 10:00 ` Christophe LEROY
2018-02-18 10:00 ` Christophe LEROY
2018-02-19 15:41 ` Daniel Vetter
2018-02-19 15:41 ` Daniel Vetter
2018-02-19 15:41 ` Daniel Vetter
2018-02-19 15:41 ` Daniel Vetter
2018-02-19 19:33 ` Pavel Machek
2018-02-19 19:33 ` Pavel Machek
2018-02-19 19:33 ` Pavel Machek
2018-02-19 19:33 ` Pavel Machek
2018-02-20 1:25 ` Rob Clark
2018-02-20 1:25 ` Rob Clark
2018-02-20 1:25 ` Rob Clark
2018-02-20 8:03 ` Jani Nikula
2018-02-20 8:03 ` Jani Nikula
2018-02-20 16:34 ` Alex Deucher
2018-02-20 16:34 ` Alex Deucher
2018-02-20 16:34 ` Alex Deucher
2018-02-20 23:47 ` Andrew Morton
2018-02-20 23:47 ` Andrew Morton
2018-02-20 23:47 ` Andrew Morton
[not found] ` <20180219154135.GV22199-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-02-19 19:33 ` Pavel Machek
2018-02-20 6:19 ` Michael Ellerman
2018-02-20 6:19 ` Michael Ellerman
2018-02-20 6:19 ` Michael Ellerman
2018-02-20 16:41 ` Joe Perches [this message]
2018-02-20 16:41 ` Joe Perches
2018-02-20 16:41 ` Joe Perches
2018-02-20 16:41 ` Joe Perches
2018-02-18 10:00 ` Christophe LEROY
2018-02-20 5:33 ` Vineet Gupta
2018-02-20 5:33 ` Vineet Gupta
2018-02-22 9:09 ` Shawn Guo
2018-02-22 9:09 ` Shawn Guo
2018-02-22 9:09 ` Shawn Guo
2018-02-24 8:52 ` Pavel Machek
2018-02-24 8:52 ` Pavel Machek
2018-02-24 8:52 ` Pavel Machek
2018-02-24 8:56 ` Shawn Guo
2018-02-24 8:56 ` Shawn Guo
2018-02-24 8:56 ` Shawn Guo
-- strict thread matches above, loose matches on Subject: below --
2018-02-17 21:19 Pavel Machek
2018-02-17 21:19 Pavel Machek
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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.