From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <julia.lawall@lip6.fr>
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 11:54:50 +0100 [thread overview]
Message-ID: <20170515105450.5yllj7elaps5b64q@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1705151838370.4315@hadrien>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Mon, May 15, 2017 at 06:41:41PM +0800, Julia Lawall wrote:
> 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.
Well, if the cover letter is needed to understand the patch then it
needs to go to everyone anyway...
> Part of the purpose of the cover letter was to allow people who were not
> interested to skip over the whole thing at once.
On the flip side things that lack context can get discarded easily.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-05-15 10:54 UTC|newest]
Thread overview: 11+ 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 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
2017-05-15 10:54 ` Mark Brown [this message]
2017-05-23 11:24 ` Applied "regulator: palmas: Drop unnecessary static" to the regulator tree Mark Brown
2017-06-27 23:47 ` [PATCH 0/9] Drop unnecessary static 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=20170515105450.5yllj7elaps5b64q@sirena.org.uk \
--to=broonie@kernel.org \
--cc=julia.lawall@lip6.fr \
--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