All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <garsilva@embeddedor.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Timur Tabi <timur@tabi.org>,
	Nicolin Chen <nicoleotsuka@gmail.com>,
	Xiubo Li <Xiubo.Lee@gmail.com>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: fsl_asrc: constify snd_soc_dai_ops structure
Date: Thu, 13 Jul 2017 10:18:14 -0500	[thread overview]
Message-ID: <20170713101814.Horde.q8OhHejhvSALVEt2o11aUTW@gator4166.hostgator.com> (raw)
In-Reply-To: <20170713101630.odml56qmsvgxqj64@sirena.org.uk>

Hi Mark,

Quoting Mark Brown <broonie@kernel.org>:

> On Thu, Jul 13, 2017 at 09:32:41AM +0200, Takashi Iwai wrote:
>
>> please stop posting in this style.  It's really annoying to see
>> spontaneously popping-up almost same patch for more than two hours
>> long.
>
>> If you have a series of the same fix patches, send them as a patch
>> set in a shot with a thread.  git-send-email does it right.
>
>> I don't mind a couple of patches posted separately, but this is over
>> the limit.
>
> Or at least just collect them up and send them all at one time even if
> not as a single thread (you don't want to CC everyone affected by a
> single patch in the set on everything, that's harder to avoid when
> sending a series via git, but it can be confusing to get one item in a
> large patch series without context).

I like this idea better. I will do so next time. :)

Thank you
--
Gustavo A. R. Silva

WARNING: multiple messages have this Message-ID (diff)
From: "Gustavo A. R. Silva" <garsilva@embeddedor.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Xiubo Li <Xiubo.Lee@gmail.com>,
	Takashi Iwai <tiwai@suse.de>,
	linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>, Timur Tabi <timur@tabi.org>,
	Nicolin Chen <nicoleotsuka@gmail.com>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] ASoC: fsl_asrc: constify snd_soc_dai_ops structure
Date: Thu, 13 Jul 2017 10:18:14 -0500	[thread overview]
Message-ID: <20170713101814.Horde.q8OhHejhvSALVEt2o11aUTW@gator4166.hostgator.com> (raw)
In-Reply-To: <20170713101630.odml56qmsvgxqj64@sirena.org.uk>

Hi Mark,

Quoting Mark Brown <broonie@kernel.org>:

> On Thu, Jul 13, 2017 at 09:32:41AM +0200, Takashi Iwai wrote:
>
>> please stop posting in this style.  It's really annoying to see
>> spontaneously popping-up almost same patch for more than two hours
>> long.
>
>> If you have a series of the same fix patches, send them as a patch
>> set in a shot with a thread.  git-send-email does it right.
>
>> I don't mind a couple of patches posted separately, but this is over
>> the limit.
>
> Or at least just collect them up and send them all at one time even if
> not as a single thread (you don't want to CC everyone affected by a
> single patch in the set on everything, that's harder to avoid when
> sending a series via git, but it can be confusing to get one item in a
> large patch series without context).

I like this idea better. I will do so next time. :)

Thank you
--
Gustavo A. R. Silva

  reply	other threads:[~2017-07-13 15:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13  7:23 [PATCH] ASoC: fsl_asrc: constify snd_soc_dai_ops structure Gustavo A. R. Silva
2017-07-13  7:23 ` Gustavo A. R. Silva
2017-07-13  7:32 ` [alsa-devel] " Takashi Iwai
2017-07-13  7:32   ` Takashi Iwai
2017-07-13  7:36   ` Gustavo A. R. Silva
2017-07-13 10:16   ` Mark Brown
2017-07-13 10:16     ` Mark Brown
2017-07-13 15:18     ` Gustavo A. R. Silva [this message]
2017-07-13 15:18       ` Gustavo A. R. Silva
2017-07-13 18:18       ` [alsa-devel] " Joe Perches
2017-07-13 18:18         ` Joe Perches
2017-07-13 21:10         ` Gustavo A. R. Silva
2017-07-13 21:10           ` Gustavo A. R. Silva
2017-07-14 11:02         ` [alsa-devel] " Mark Brown
2017-07-14 11:08           ` Joe Perches
2017-07-14 11:08             ` Joe Perches
2017-07-14 11:25             ` Mark Brown
2017-07-17  4:22               ` Gustavo A. R. Silva
2017-07-17 16:05 ` Applied "ASoC: fsl_asrc: constify snd_soc_dai_ops structure" to the asoc tree Mark Brown
2017-07-17 16:05   ` 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=20170713101814.Horde.q8OhHejhvSALVEt2o11aUTW@gator4166.hostgator.com \
    --to=garsilva@embeddedor.com \
    --cc=Xiubo.Lee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nicoleotsuka@gmail.com \
    --cc=perex@perex.cz \
    --cc=timur@tabi.org \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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.