All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Mc Guire <der.herr@hofr.at>
To: Mark Brown <broonie@kernel.org>
Cc: Nicholas Mc Guire <hofrat@osadl.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Xiubo Li <Li.Xiubo@freescale.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Axel Lin <axel.lin@ingics.com>,
	abdoulaye berthe <berthe.ab@gmail.com>,
	patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: wm5100: match wait_for_completion_timeout return type
Date: Mon, 9 Mar 2015 07:22:26 +0100	[thread overview]
Message-ID: <20150309062226.GA9226@opentech.at> (raw)
In-Reply-To: <20150308184902.GT28806@sirena.org.uk>

On Sun, 08 Mar 2015, Mark Brown wrote:

> On Sun, Mar 08, 2015 at 06:57:07AM -0400, Nicholas Mc Guire wrote:
> > return type of wait_for_completion_timeout is unsigned long not int. An
> > appropriately named unsigned long is added and the assignment fixed up.
> 
> You are sending these to a very large CC list many of whom have no
> obvious connection to the driver - please take care to ensure that the
> people you are sending patches to are likely to want to review the code,
> this helps keep people's mailboxes less noisy.

sorry if I messed that up - my understanding was that
it should go out to all that scripts/get_mainteiner.pl shows
for the espective file. Should some of those listed
not be put on the CC list - or only maintainers+mailinglists ?

thx!
hofrat

  reply	other threads:[~2015-03-09  6:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 10:57 [PATCH] ASoC: wm5100: match wait_for_completion_timeout return type Nicholas Mc Guire
2015-03-08 10:57 ` Nicholas Mc Guire
2015-03-08 18:49 ` Mark Brown
2015-03-09  6:22   ` Nicholas Mc Guire [this message]
2015-03-09 11:26     ` Mark Brown
2015-03-09 14:29 ` Charles Keepax
2015-03-09 18:16 ` 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=20150309062226.GA9226@opentech.at \
    --to=der.herr@hofr.at \
    --cc=Li.Xiubo@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=axel.lin@ingics.com \
    --cc=berthe.ab@gmail.com \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=hofrat@osadl.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=perex@perex.cz \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tiwai@suse.de \
    --cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.