From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>,
<linux-renesas-soc@vger.kernel.org>
Subject: Re: How to post cleanup patches ?
Date: Thu, 4 Aug 2016 00:22:33 +0000 [thread overview]
Message-ID: <87vazhmltz.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20160803105611.GO10376@sirena.org.uk>
Hi Mark
> > But my concern is that you hate big-patch-set, and it is almost 70 patches.
> > Can I post these patches to ML ? or should I use git pull request ? or I shouldn't post ?
>
> A very repetitive patch series which does the same thing to multiple
> drivers (so is essentially the same patch lots of times) is not such a
> problem, the problem is huge numbers of different patches that all need
> individual review.
OK, I see
I will post it to ML
WARNING: multiple messages have this Message-ID (diff)
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>,
linux-renesas-soc@vger.kernel.org
Subject: Re: How to post cleanup patches ?
Date: Thu, 4 Aug 2016 00:22:33 +0000 [thread overview]
Message-ID: <87vazhmltz.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20160803105611.GO10376@sirena.org.uk>
Hi Mark
> > But my concern is that you hate big-patch-set, and it is almost 70 patches.
> > Can I post these patches to ML ? or should I use git pull request ? or I shouldn't post ?
>
> A very repetitive patch series which does the same thing to multiple
> drivers (so is essentially the same patch lots of times) is not such a
> problem, the problem is huge numbers of different patches that all need
> individual review.
OK, I see
I will post it to ML
next prev parent reply other threads:[~2016-08-04 0:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 1:12 How to post cleanup patches ? Kuninori Morimoto
2016-08-03 1:12 ` Kuninori Morimoto
2016-08-03 1:13 ` [PATCH 1/xx][sample] ASoC: add COMPONENT_FUNC() macro for snd_soc_component_driver Kuninori Morimoto
2016-08-03 1:13 ` Kuninori Morimoto
2016-08-03 19:16 ` [alsa-devel] " Lars-Peter Clausen
2016-08-04 0:39 ` Kuninori Morimoto
2016-08-04 0:39 ` Kuninori Morimoto
2016-08-03 1:13 ` [PATCH 2/xx][sample] ASoC: codec duplicated callback function goes to component on wm8978 Kuninori Morimoto
2016-08-03 1:13 ` Kuninori Morimoto
2016-08-03 5:16 ` [alsa-devel] " kbuild test robot
2016-08-03 1:14 ` [PATCH 3/xx][sample] ASoC: remove codec duplicated callback function Kuninori Morimoto
2016-08-03 1:14 ` Kuninori Morimoto
2016-08-03 5:48 ` [alsa-devel] " kbuild test robot
2016-08-08 11:06 ` Applied "ASoC: remove codec duplicated callback function" to the asoc tree Mark Brown
2016-08-08 11:06 ` Mark Brown
2016-08-03 10:56 ` How to post cleanup patches ? Mark Brown
2016-08-04 0:22 ` Kuninori Morimoto [this message]
2016-08-04 0:22 ` Kuninori Morimoto
2016-08-03 19:20 ` [alsa-devel] " Lars-Peter Clausen
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=87vazhmltz.wl%kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=lgirdwood@gmail.com \
--cc=linux-renesas-soc@vger.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 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.