From: Eric Engestrom <eric.engestrom@imgtec.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Russell King <linux@arm.linux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Alexander Shiyan <shc_work@mail.ru>,
Krzysztof Halasa <khalasa@piap.pl>, Sekhar Nori <nsekhar@ti.com>,
Kevin Hilman <khilman@kernel.org>,
Roland Stigge <stigge@antcom.de>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Rajendra Nayak <rnayak@ti.com>, Paul Walmsley <paul@pwsan.com>,
Tony Lindgren <tony@atomide.com>,
Viresh Kumar <vireshk@kernel.org>,
Shiraz Hashim <shiraz.linux.kernel@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Linus
Subject: Re: [PATCH 4/4] ARM: remove duplicate const qualifier
Date: Mon, 25 Apr 2016 11:39:11 +0100 [thread overview]
Message-ID: <20160425103911.GO32731@imgtec.com> (raw)
In-Reply-To: <20160425095715.GA2366@piout.net>
On Mon, Apr 25, 2016 at 11:57:15AM +0200, Alexandre Belloni wrote:
> Hi,
>
> this requires a commit message.
OK? This seems rather pointless in this case (and even more so for the
typo fix I sent yesterday), but I guess you have some general rule to
enforce. Would this do then?
"The second `const` is unnecessary, and is simply ignored by most compilers."
> Also, you should think about separating those changes in multiple patches
> to ease inclusion in the kernel.
I'll resend patch #4 as multiple patches. What the way proper to convey
that *multiple* new patches replace *one* old one? Is it enough to just
send those as a reply to this one?
Cheers
WARNING: multiple messages have this Message-ID (diff)
From: eric.engestrom@imgtec.com (Eric Engestrom)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: remove duplicate const qualifier
Date: Mon, 25 Apr 2016 11:39:11 +0100 [thread overview]
Message-ID: <20160425103911.GO32731@imgtec.com> (raw)
In-Reply-To: <20160425095715.GA2366@piout.net>
On Mon, Apr 25, 2016 at 11:57:15AM +0200, Alexandre Belloni wrote:
> Hi,
>
> this requires a commit message.
OK? This seems rather pointless in this case (and even more so for the
typo fix I sent yesterday), but I guess you have some general rule to
enforce. Would this do then?
"The second `const` is unnecessary, and is simply ignored by most compilers."
> Also, you should think about separating those changes in multiple patches
> to ease inclusion in the kernel.
I'll resend patch #4 as multiple patches. What the way proper to convey
that *multiple* new patches replace *one* old one? Is it enough to just
send those as a reply to this one?
Cheers
WARNING: multiple messages have this Message-ID (diff)
From: Eric Engestrom <eric.engestrom@imgtec.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: <linux-kernel@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Russell King <linux@arm.linux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Alexander Shiyan <shc_work@mail.ru>,
Krzysztof Halasa <khalasa@piap.pl>, Sekhar Nori <nsekhar@ti.com>,
Kevin Hilman <khilman@kernel.org>,
Roland Stigge <stigge@antcom.de>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Rajendra Nayak <rnayak@ti.com>, Paul Walmsley <paul@pwsan.com>,
Tony Lindgren <tony@atomide.com>,
Viresh Kumar <vireshk@kernel.org>,
Shiraz Hashim <shiraz.linux.kernel@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<bcm-kernel-feedback-list@broadcom.com>,
<linux-omap@vger.kernel.org>, <spear-devel@list.st.com>
Subject: Re: [PATCH 4/4] ARM: remove duplicate const qualifier
Date: Mon, 25 Apr 2016 11:39:11 +0100 [thread overview]
Message-ID: <20160425103911.GO32731@imgtec.com> (raw)
In-Reply-To: <20160425095715.GA2366@piout.net>
On Mon, Apr 25, 2016 at 11:57:15AM +0200, Alexandre Belloni wrote:
> Hi,
>
> this requires a commit message.
OK? This seems rather pointless in this case (and even more so for the
typo fix I sent yesterday), but I guess you have some general rule to
enforce. Would this do then?
"The second `const` is unnecessary, and is simply ignored by most compilers."
> Also, you should think about separating those changes in multiple patches
> to ease inclusion in the kernel.
I'll resend patch #4 as multiple patches. What the way proper to convey
that *multiple* new patches replace *one* old one? Is it enough to just
send those as a reply to this one?
Cheers
next prev parent reply other threads:[~2016-04-25 10:39 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 9:47 [PATCH 1/4] perf tools: remove duplicate const qualifier Eric Engestrom
2016-04-25 9:47 ` [PATCH 2/4] drivers: firmware: psci: " Eric Engestrom
2016-04-25 9:47 ` Eric Engestrom
2016-04-25 10:33 ` Jisheng Zhang
2016-04-25 10:33 ` Jisheng Zhang
2016-04-25 9:47 ` [PATCH 3/4] dmaengine: pxa_dma: " Eric Engestrom
2016-04-25 9:47 ` Eric Engestrom
2016-04-25 19:18 ` Robert Jarzmik
2016-04-25 19:18 ` Robert Jarzmik
2016-04-26 16:30 ` Vinod Koul
2016-04-26 16:30 ` Vinod Koul
2016-04-25 9:47 ` [PATCH 4/4] ARM: " Eric Engestrom
2016-04-25 9:47 ` Eric Engestrom
2016-04-25 9:47 ` Eric Engestrom
2016-04-25 9:52 ` Viresh Kumar
2016-04-25 9:52 ` Viresh Kumar
2016-04-25 9:52 ` Viresh Kumar
2016-04-25 9:57 ` Alexandre Belloni
2016-04-25 9:57 ` Alexandre Belloni
2016-04-25 9:57 ` Alexandre Belloni
2016-04-25 10:39 ` Eric Engestrom [this message]
2016-04-25 10:39 ` Eric Engestrom
2016-04-25 10:39 ` Eric Engestrom
2016-04-25 11:38 ` Arnd Bergmann
2016-04-25 11:38 ` Arnd Bergmann
2016-04-25 11:38 ` Arnd Bergmann
2016-04-25 12:58 ` Eric Engestrom
2016-04-25 12:58 ` Eric Engestrom
2016-04-25 12:58 ` Eric Engestrom
2016-04-25 14:12 ` Nicolas Pitre
2016-04-25 14:12 ` Nicolas Pitre
2016-04-25 14:12 ` Nicolas Pitre
2016-04-25 14:37 ` Eric Engestrom
2016-04-25 14:37 ` Eric Engestrom
2016-04-25 14:37 ` Eric Engestrom
2016-04-26 10:12 ` Krzysztof Hałasa
2016-04-26 10:12 ` Krzysztof Hałasa
2016-04-26 10:12 ` Krzysztof Hałasa
2016-04-27 20:01 ` Nicolas Pitre
2016-04-27 20:01 ` Nicolas Pitre
2016-04-27 20:01 ` Nicolas Pitre
2016-04-25 10:59 ` Sylvain Lemieux
2016-04-25 10:59 ` Sylvain Lemieux
2016-04-25 10:59 ` Sylvain Lemieux
2016-04-25 21:11 ` [PATCH 1/4] perf tools: " Arnaldo Carvalho de Melo
2016-04-27 15:32 ` [tip:perf/core] perf tools: Remove " tip-bot for Eric Engestrom
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=20160425103911.GO32731@imgtec.com \
--to=eric.engestrom@imgtec.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=k.kozlowski@samsung.com \
--cc=kernel@pengutronix.de \
--cc=khalasa@piap.pl \
--cc=khilman@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.ferre@atmel.com \
--cc=nicolas.pitre@linaro.org \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=plagnioj@jcrosoft.com \
--cc=rjui@broadcom.com \
--cc=rnayak@ti.com \
--cc=sbranden@broadcom.com \
--cc=shawnguo@kernel.org \
--cc=shc_work@mail.ru \
--cc=shiraz.linux.kernel@gmail.com \
--cc=stigge@antcom.de \
--cc=tony@atomide.com \
--cc=vireshk@kernel.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 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.