* submiting an asoc-core patch with codec updates
@ 2012-03-29 19:23 Brian Austin
2012-03-29 21:24 ` Mark Brown
0 siblings, 1 reply; 2+ messages in thread
From: Brian Austin @ 2012-03-29 19:23 UTC (permalink / raw)
To: alsa-devel; +Cc: broonie
I would like to submit a patch that adds some new macros for TLV in ASoC.
this patch requires changes in 2 codecs (CS42L51,CS42L73).
Should I submit just the asoc-core patch then follow up with the codec
patches or just submit as a series?
Thanks,
Brian
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: submiting an asoc-core patch with codec updates
2012-03-29 19:23 submiting an asoc-core patch with codec updates Brian Austin
@ 2012-03-29 21:24 ` Mark Brown
0 siblings, 0 replies; 2+ messages in thread
From: Mark Brown @ 2012-03-29 21:24 UTC (permalink / raw)
To: Brian Austin; +Cc: alsa-devel
[-- Attachment #1.1: Type: text/plain, Size: 639 bytes --]
On Thu, Mar 29, 2012 at 02:23:59PM -0500, Brian Austin wrote:
> I would like to submit a patch that adds some new macros for TLV in
> ASoC. this patch requires changes in 2 codecs (CS42L51,CS42L73).
> Should I submit just the asoc-core patch then follow up with the
> codec patches or just submit as a series?
If the core patch doesn't break the build of the CODECs (eg, it
introduces a new API) either way is fine, it doesn't matter much so long
as it's clear that the core patch needs to be applied first. If the
core patch does break the build (eg, it changes an existing API) then
all the changes need to be part of a single patch.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-03-29 21:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-29 19:23 submiting an asoc-core patch with codec updates Brian Austin
2012-03-29 21:24 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).