From: Mark Brown <broonie@kernel.org>
To: Steve Lee <SteveS.Lee@maximintegrated.com>
Cc: "jack.yu@realtek.com" <jack.yu@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"ryan.lee.maxim@gmail.com" <ryan.lee.maxim@gmail.com>,
"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
Ryan Lee <RyanS.Lee@maximintegrated.com>,
"steves.lee.maxim@gmail.com" <steves.lee.maxim@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tiwai@suse.com" <tiwai@suse.com>,
"krzk@kernel.org" <krzk@kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"nuno.sa@analog.com" <nuno.sa@analog.com>,
"geert@linux-m68k.org" <geert@linux-m68k.org>,
"dmurphy@ti.com" <dmurphy@ti.com>,
"shumingf@realtek.com" <shumingf@realtek.com>,
"srinivas.kandagatla@linaro.org" <srinivas.kandagatla@linaro.org>,
"rf@opensource.wolfsonmicro.com" <rf@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 3/3] ASoC: max98390: update dsm param bin max size
Date: Mon, 27 Jul 2020 14:07:34 +0100 [thread overview]
Message-ID: <20200727130734.GD6275@sirena.org.uk> (raw)
In-Reply-To: <MWHPR11MB204753BF80DED8923AD3BEA292720@MWHPR11MB2047.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
On Mon, Jul 27, 2020 at 02:00:09AM +0000, Steve Lee wrote:
> > I'm missing patches 1-2 and have no cover letter - what's the story with
> > dependencies?
> I will re-send patch ang please ignore this patch.
> DSM init param is extended to cover more register so that DSM MAX PARAM SIZE value is changed.
I applied these on Friday having found the other two patches (you're not
sending things as a thread so they get lost, for example if someone
sends a big series at a similar time like what happened on Friday) so
your new version won't apply, please resend whatever change you want to
make as an incremental patch against current code.
Please do not submit new versions of already applied patches, please
submit incremental updates to the existing code. Modifying existing
commits creates problems for other users building on top of those
commits so it's best practice to only change pubished git commits if
absolutely essential.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-27 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 8:56 [PATCH 3/3] ASoC: max98390: update dsm param bin max size Steve Lee
2020-07-24 10:50 ` Mark Brown
2020-07-27 2:00 ` Steve Lee
2020-07-27 13:07 ` Mark Brown [this message]
2020-07-28 1:14 ` Steve Lee
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=20200727130734.GD6275@sirena.org.uk \
--to=broonie@kernel.org \
--cc=RyanS.Lee@maximintegrated.com \
--cc=SteveS.Lee@maximintegrated.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=dmurphy@ti.com \
--cc=geert@linux-m68k.org \
--cc=jack.yu@realtek.com \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=rf@opensource.wolfsonmicro.com \
--cc=ryan.lee.maxim@gmail.com \
--cc=shumingf@realtek.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=steves.lee.maxim@gmail.com \
--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