From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, vkoul@kernel.org
Subject: Re: [PATCH] ASoC: codecs: nau8825: fix kernel-doc
Date: Mon, 1 Mar 2021 11:42:07 -0600 [thread overview]
Message-ID: <79796455-2aa8-7873-31d1-e5bae6e49dc4@linux.intel.com> (raw)
In-Reply-To: <20210301171416.GF4628@sirena.org.uk>
On 3/1/21 11:14 AM, Mark Brown wrote:
> On Mon, Mar 01, 2021 at 10:53:46AM -0600, Pierre-Louis Bossart wrote:
>> v5.12-rc1 flags new warnings with make W=1, fix missing or broken
>> function descriptors.
>
> You've sent five patches (for multiple subsystems) in a thread but not
> as a series - please don't do this, it confuses tools like b4 since they
> can't figure out if this is a series or multiple revisions of a single
> patch. Please don't do this, if things are a series send them as such
> or if it's a collection of unrelated patches send them separately.
Humm yes, I thought git sendmail would be smart enough to detect it
wasn't a series...oh well, will resend a v2.
next prev parent reply other threads:[~2021-03-01 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:53 [PATCH] ALSA: hda: fix kernel-doc warnings Pierre-Louis Bossart
2021-03-01 16:53 ` [PATCH] ASoC: codecs: nau8825: fix kernel-doc Pierre-Louis Bossart
2021-03-01 17:14 ` Mark Brown
2021-03-01 17:42 ` Pierre-Louis Bossart [this message]
2021-03-01 16:53 ` [PATCH] ASoC: Intel: atom: " Pierre-Louis Bossart
2021-03-04 0:54 ` Mark Brown
2021-03-01 16:53 ` [PATCH] ASoC: soc-dai: " Pierre-Louis Bossart
2021-03-01 16:53 ` [PATCH] soundwire: cadence_master: " Pierre-Louis Bossart
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=79796455-2aa8-7873-31d1-e5bae6e49dc4@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=tiwai@suse.de \
--cc=vkoul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox