Messages in this thread | | | From | Steve Lee <> | Subject | RE: [PATCH 3/3] ASoC: max98390: update dsm param bin max size | Date | Tue, 28 Jul 2020 01:14:27 +0000 |
| |
> -----Original Message----- > From: Mark Brown <broonie@kernel.org> > Sent: Monday, July 27, 2020 10:08 PM > To: Steve Lee <SteveS.Lee@maximintegrated.com> > Cc: lgirdwood@gmail.com; perex@perex.cz; tiwai@suse.com; > ckeepax@opensource.cirrus.com; geert@linux-m68k.org; > rf@opensource.wolfsonmicro.com; shumingf@realtek.com; > srinivas.kandagatla@linaro.org; krzk@kernel.org; dmurphy@ti.com; > jack.yu@realtek.com; nuno.sa@analog.com; linux-kernel@vger.kernel.org; > alsa-devel@alsa-project.org; ryan.lee.maxim@gmail.com; Ryan Lee > <RyanS.Lee@maximintegrated.com>; steves.lee.maxim@gmail.com > Subject: Re: [PATCH 3/3] ASoC: max98390: update dsm param bin max size > > 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.
Thanks, I missed patched was already applied. I will send patch upon these patches later.
| |