From: Mark Brown <broonie@kernel.org>
To: Mathias Krause <minipli@googlemail.com>
Cc: alsa-devel@alsa-project.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Liam Girdwood <lgirdwood@gmail.com>, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 0/4] ASoC: constification patches
Date: Mon, 15 Jun 2015 20:17:31 +0100 [thread overview]
Message-ID: <20150615191731.GD18309@sirena.org.uk> (raw)
In-Reply-To: <CA+rthh9Lbqwmc4o9Qbx4gZz-OSmuCY275YXdkmumwQxugkENtQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 565 bytes --]
On Mon, Jun 15, 2015 at 07:59:30PM +0200, Mathias Krause wrote:
> Sorry, actually I tried to. It's what get_maintainer.pl told me but I
> tried to trim down the list because of the simpleness of the patches.
> I omitted LKML to avoid cross-posting. I messed up patches 2 and 3,
> admitted. But what else was wrong?
I can't remember now, perhaps it was just the second Realtek patch.
Like I say you shouldn't treat get_maintainer.pl as reliable (it can be
a good start but without --git it often misses people and with --git it
gets way too many false positives).
[-- 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-06-15 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 12:25 [PATCH 0/4] ASoC: constification patches Mathias Krause
2015-06-13 12:25 ` [PATCH 1/4] ASoC: max98090: Constify ACPI device ids and register map Mathias Krause
2015-06-13 12:25 ` [PATCH 2/4] ASoC: rt5640: " Mathias Krause
2015-06-15 10:19 ` Mark Brown
2015-06-15 17:50 ` Mathias Krause
2015-06-13 12:25 ` [PATCH 3/4] ASoC: rt5670: " Mathias Krause
2015-06-13 12:25 ` [PATCH 4/4] ASoC: intel: Constify ACPI device ids Mathias Krause
2015-06-15 13:07 ` Jarkko Nikula
2015-06-15 10:32 ` [PATCH 0/4] ASoC: constification patches Mark Brown
2015-06-15 17:59 ` Mathias Krause
2015-06-15 19:17 ` 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=20150615191731.GD18309@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lenb@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=minipli@googlemail.com \
--cc=rjw@rjwysocki.net \
/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