From: Mark Brown <broonie@kernel.org>
To: Antonio Ospite <ao2@ao2.it>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH 05/12] trivial: ASoC: adau1977: fix typo s/Substraction/Subtraction/
Date: Wed, 29 Apr 2015 11:23:49 +0100 [thread overview]
Message-ID: <20150429102349.GA22845@sirena.org.uk> (raw)
In-Reply-To: <20150428232758.28e194be2c9a3d61be23f4bc@ao2.it>
[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]
On Tue, Apr 28, 2015 at 11:27:58PM +0200, Antonio Ospite wrote:
> I tried to follow the subject style for the subsystem, but then I
> prefixed it with "trivial" to highlight that I was sending an aggregate
> set of unrelated patches to trivial@kernel.org, that's also why I didn't
> want to CC everyone on every patch: to reduce noise.
That's not really helpful - it means that the patch is more likely to be
missed and that the patch sticks out in the changelog.
> Maybe involving trivial@kernel.org for changes which apply to a
> _specific_ subsystem is not necessary at all, next time I will just
> aggregate by subsystem.
That's generally better, the expectation should be that maintainers are
going to apply even trivial patches and it does make life easier if
things go that way (less chance of conflicting changes for example).
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-04-29 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430219491-5076-1-git-send-email-ao2@ao2.it>
2015-04-28 11:11 ` [PATCH 03/12] trivial: ASoC: pxa: pxa-ssp.c: indent with TABs, not spaces Antonio Ospite
2015-04-28 11:11 ` [PATCH 05/12] trivial: ASoC: adau1977: fix typo s/Substraction/Subtraction/ Antonio Ospite
2015-04-28 12:20 ` Lars-Peter Clausen
2015-04-28 16:00 ` Mark Brown
2015-04-28 21:27 ` Antonio Ospite
2015-04-29 10:23 ` Mark Brown [this message]
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=20150429102349.GA22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ao2@ao2.it \
--cc=lars@metafoo.de \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox