From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Brian Austin <brian.austin@cirrus.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: submiting an asoc-core patch with codec updates
Date: Thu, 29 Mar 2012 22:24:04 +0100 [thread overview]
Message-ID: <20120329212403.GA4153@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1203291421530.21413@heelrod.ad.cirrus.com>
[-- 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 --]
prev parent reply other threads:[~2012-03-29 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 19:23 submiting an asoc-core patch with codec updates Brian Austin
2012-03-29 21:24 ` Mark Brown [this message]
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=20120329212403.GA4153@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.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;
as well as URLs for NNTP newsgroup(s).