From: Mark Brown <broonie@kernel.org>
To: "Sarha, Jyri" <jyri.sarha@intel.com>
Cc: "peter.ujfalusi@linux.intel.com" <peter.ujfalusi@linux.intel.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"pierre-louis.bossart@linux.intel.com"
<pierre-louis.bossart@linux.intel.com>,
"kai.vehmanen@linux.intel.com" <kai.vehmanen@linux.intel.com>,
"Wang, Rander" <rander.wang@intel.com>,
"ranjani.sridharan@linux.intel.com"
<ranjani.sridharan@linux.intel.com>,
"error27@gmail.com" <error27@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v2 0/3] ASoC: SOF: ipc4/intel: Support for ChainDMA
Date: Wed, 22 Mar 2023 15:27:57 +0000 [thread overview]
Message-ID: <ZBsefQsoRHJDiju2@sirena.org.uk> (raw)
In-Reply-To: <578daea5b7bc0db3164c84e550b24bd724de9ebe.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Wed, Mar 22, 2023 at 03:15:23PM +0000, Sarha, Jyri wrote:
> On Wed, 2023-03-22 at 14:04 +0000, Mark Brown wrote:
> > 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.
> Hi Mark,
> Would a git fixup patch do at this phase, or should we do just a
> regular patch with
To repeat what's quoted above "please submit incremental updates
to the existing code".
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-22 15:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 13:59 [PATCH v2 0/3] ASoC: SOF: ipc4/intel: Support for ChainDMA Peter Ujfalusi
2023-03-22 13:59 ` [PATCH v2 1/3] ASoC: SOF: topology: Set pipeline widget before updating IPC structures Peter Ujfalusi
2023-03-22 13:59 ` [PATCH v2 2/3] ASoC: SOF: ipc4: Add macros for chain-dma message bits Peter Ujfalusi
2023-03-22 13:59 ` [PATCH v2 3/3] ASoC: SOF: ipc4/intel: Add support for chained DMA Peter Ujfalusi
2023-03-22 14:04 ` [PATCH v2 0/3] ASoC: SOF: ipc4/intel: Support for ChainDMA Mark Brown
2023-03-22 15:15 ` Sarha, Jyri
2023-03-22 15:27 ` Mark Brown [this message]
2023-03-23 7:13 ` Péter Ujfalusi
-- strict thread matches above, loose matches on Subject: below --
2023-03-22 13:58 Peter Ujfalusi
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=ZBsefQsoRHJDiju2@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=error27@gmail.com \
--cc=jyri.sarha@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@intel.com \
--cc=ranjani.sridharan@linux.intel.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 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.