From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Rene Herman <rene.herman@keyaccess.nl>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/5] asihpi: Add new HPI apis for sampleclock, tuner
Date: Thu, 6 Mar 2008 10:17:04 +0000 [thread overview]
Message-ID: <20080306101702.GA30114@sirena.org.uk> (raw)
In-Reply-To: <s5hpru82mad.wl%tiwai@suse.de>
On Thu, Mar 06, 2008 at 11:12:58AM +0100, Takashi Iwai wrote:
> Besides that, in general it's recommended to add relevent developers
> to Cc's if you post patches. Then patches reach directly to the
> developers and have more chances to get in more quickly and
> certainly.
But note that there are a few subsystem maintainers who don't like this
so it's worth looking at what other people submitting patches for the
subsystem are doing.
next prev parent reply other threads:[~2008-03-06 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 1:51 [PATCH 5/5] asihpi: add hwdep (experimental) Eliot Blennerhassett
2008-03-06 2:07 ` [PATCH 2/5] asihpi: Add new HPI apis for sampleclock, tuner Eliot Blennerhassett
2008-03-06 9:50 ` Takashi Iwai
2008-03-06 10:05 ` Rene Herman
2008-03-06 10:12 ` Takashi Iwai
2008-03-06 10:17 ` Mark Brown [this message]
2008-03-06 10:24 ` Takashi Iwai
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=20080306101702.GA30114@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=rene.herman@keyaccess.nl \
--cc=tiwai@suse.de \
/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