From: "Måns Rullgård" <mans@mansr.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: mxs-saif: check BUSY bit in hw_params() only if not mclk_in_use
Date: Fri, 05 Feb 2016 13:43:22 +0000 [thread overview]
Message-ID: <yw1xwpqjgtmt.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <20160205133712.GC12311@sirena.org.uk> (Mark Brown's message of "Fri, 5 Feb 2016 13:37:12 +0000")
Mark Brown <broonie@kernel.org> writes:
> On Fri, Feb 05, 2016 at 01:23:20PM +0000, Måns Rullgård wrote:
>> Mark Brown <broonie@kernel.org> writes:
>
>> > Please remember to CC the maintainers for the driver when sending
>> > patches.
>
>> I CCd everybody scripts/get_maintainers.pl suggested. How am I supposed
>> to know who the maintainers are if they're not listed in MAINTAINERS?
>
> By looking at people working on the driver in git and the authors listed
> in the driver (get_maintainer --git will do most of this for you, though
> you do have to think about false positives). As previously advised this
> is not something that can be fully automated, you need to think about
> who you are sending things to and why.
Most files have been touched by many people. I thought the entire point
of the MAINTAINERS file was to remove the guesswork from choosing where
to send patches. Apparently sound/ has rules of its own.
--
Måns Rullgård
next prev parent reply other threads:[~2016-02-05 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 13:18 Mans Rullgard
2016-02-05 13:19 ` Mark Brown
2016-02-05 13:23 ` Måns Rullgård
2016-02-05 13:37 ` Mark Brown
2016-02-05 13:43 ` Måns Rullgård [this message]
2016-02-05 16:00 ` Mark Brown
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=yw1xwpqjgtmt.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®