From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [PATCH 2/5] asihpi: Add new HPI apis for sampleclock, tuner Date: Thu, 06 Mar 2008 11:24:15 +0100 Message-ID: References: <200803061451.18758.linux@audioscience.com> <200803061507.54147.linux@audioscience.com> <47CFC1F4.1060705@keyaccess.nl> <20080306101702.GA30114@sirena.org.uk> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (ns2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 2FC72244A0 for ; Thu, 6 Mar 2008 11:24:16 +0100 (CET) In-Reply-To: <20080306101702.GA30114@sirena.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: Rene Herman , alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Thu, 6 Mar 2008 10:17:04 +0000, Mark Brown wrote: > > 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. Yeah there are always exceptions :) But, *in general*, Cc to developers is a good thing. BTW, this doesn't mean that you don't send patches to ML. The patches should be sent to ML, and Cc to maintainers/developers. Takashi