From: Julia Lawall <julia.lawall@lip6.fr>
To: Mark Brown <broonie@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>,
keescook@chromium.org, kernel-janitors@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/9] regulator: palmas: Drop unnecessary static
Date: Mon, 15 May 2017 10:41:41 +0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1705151838370.4315@hadrien> (raw)
In-Reply-To: <20170514101323.235p6jflfproucmv@sirena.org.uk>
On Sun, 14 May 2017, Mark Brown wrote:
> On Thu, May 04, 2017 at 10:10:51PM +0200, Julia Lawall wrote:
> > Drop static on a local variable, when the variable is initialized before
> > any use, on every possible execution path through the function.
>
> When sending a bunch of changes like this please either send the cover
> letter to everyone or send each patch separately (this seems like it
> stands alone just fine). The first question when only one patch in a
> series is visible is always what are the interdependencies.
Not sure what is best to do. If the cover letter goes to everyone, it
could be rejected for too many recipients. Currently it goes to all the
mailing lists. If the patches are sent separately, then could there be a
cover letter for each one? If the semantic patch is complicated, then I
typically put the whole thing there, and an abbreviated one in the actual
patch. That is not relevant here, because the semantic patch is small.
Part of the purpose of the cover letter was to allow people who were not
interested to skip over the whole thing at once.
julia
next prev parent reply other threads:[~2017-05-15 10:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 20:10 [PATCH 0/9] Drop unnecessary static Julia Lawall
2017-05-04 20:10 ` [PATCH 1/9] mtd: cfi_cmdset_0020: " Julia Lawall
2017-05-11 18:49 ` Brian Norris
2017-05-04 20:10 ` [PATCH 2/9] mtd: physmap_of: " Julia Lawall
2017-05-04 20:10 ` [PATCH 3/9] drbd: " Julia Lawall
2017-05-05 7:19 ` Roland Kammerer
2017-06-27 23:49 ` Kees Cook
2017-06-27 23:58 ` Jens Axboe
2017-05-04 20:10 ` [PATCH 4/9] power: supply: axp20x_usb_power: " Julia Lawall
2017-05-15 13:25 ` Sebastian Reichel
2017-05-04 20:10 ` [PATCH 5/9] mfd: " Julia Lawall
2017-06-27 23:46 ` Kees Cook
2017-07-03 11:42 ` Lee Jones
2017-07-17 11:01 ` Lee Jones
2017-05-04 20:10 ` [PATCH 6/9] regulator: palmas: " Julia Lawall
2017-05-14 10:13 ` Mark Brown
2017-05-15 10:41 ` Julia Lawall [this message]
2017-05-15 10:54 ` Mark Brown
2017-05-23 11:24 ` Applied "regulator: palmas: Drop unnecessary static" to the regulator tree Mark Brown
2017-05-04 20:10 ` [PATCH 7/9] iio: hid-sensor-accel-3d: Drop unnecessary static Julia Lawall
2017-05-07 12:57 ` Jonathan Cameron
2017-05-04 20:10 ` [PATCH 8/9] clocksource/drivers/fttmr010: " Julia Lawall
2017-06-27 23:45 ` Kees Cook
2017-05-04 20:10 ` [PATCH 9/9] mfd: max8925-i2c: " Julia Lawall
2017-06-27 23:47 ` Kees Cook
2017-07-03 11:42 ` Lee Jones
2017-07-17 11:00 ` Lee Jones
2017-06-27 23:47 ` [PATCH 0/9] " Kees Cook
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=alpine.DEB.2.20.1705151838370.4315@hadrien \
--to=julia.lawall@lip6.fr \
--cc=broonie@kernel.org \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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