From: Takashi Iwai <tiwai@suse.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/5] asihpi: Add new HPI apis for sampleclock, tuner
Date: Thu, 06 Mar 2008 11:12:58 +0100 [thread overview]
Message-ID: <s5hpru82mad.wl%tiwai@suse.de> (raw)
In-Reply-To: <47CFC1F4.1060705@keyaccess.nl>
At Thu, 06 Mar 2008 11:05:40 +0100,
Rene Herman wrote:
>
> On 06-03-08 10:50, Takashi Iwai wrote:
>
> > At Thu, 06 Mar 2008 15:07:54 +1300,
> > Eliot Blennerhassett wrote:
>
> >> Patch 2/5 is waiting moderator approval (its 90K)
> >
> > Add my address to Cc at the next time so that I get patches directly.
>
> I've emailed Jaroslav a number of times asking to up the limit but have as
> usual seen them disappear into the great perex email blackhole. By now I'm
> simply rejecting them, asking posters to contact Jaroslav themselves...
>
> The limit's at 60K right now which has been too little for quite a few valid
> patches. I believe that upto now 200K should mostly do but haven't in fact
> seen anything being size-moderated which _wasn't_ valid list content -- the
> size moderation category seems fairly useless to start with therefore.
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.
Takashi
next prev parent reply other threads:[~2008-03-06 10:12 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 [this message]
2008-03-06 10:17 ` Mark Brown
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=s5hpru82mad.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=rene.herman@keyaccess.nl \
/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