Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mznyfn@0pointer.de>
To: alsa-devel@alsa-project.org
Subject: Re: Pull request for alsa-plugins
Date: Thu, 4 Sep 2008 16:03:39 +0200	[thread overview]
Message-ID: <20080904140339.GC31516@tango.0pointer.de> (raw)
In-Reply-To: <s5h63pcnygu.wl%tiwai@suse.de>

On Thu, 04.09.08 09:48, Takashi Iwai (tiwai@suse.de) wrote:

> > please pull and merge a series of 26 patches for alsa-plugins'
> > PulseAudio driver which I prepared in this repository of mine:
> > 
> >     git://git.0pointer.de/alsa-plugins.git
> 
> Thanks, pulled in, pushed out now.
> 
> At the next time, could you add our sign-off to each commit?
> I don't care much about it for non-kernel codes, but certainly better
> with it.

Sure, will do.

> Also, please add the branch name in the same line of git://... above.
> The recent git requires the branch name explicitly to pull.

Will do.

> One of my concerns in the current pulse code is the many use of
> assert().  In many cases, assert() is a wrong choice.  For example,
> checking the return value of malloc in assert() is definitely wrong.
> It should be always checked, and should return an error instead of
> aborting the program.

I think I fixed every single assert() on malloc, OOM should now be
handled in similar way to most other code in in
alsa-lib/-plugins. 

Still, there are quite a few asserts left in the pulse driver which
check validity of function parameters. But they should only be hit on
internal programming errors and as such I think it makes a lot of
sense to leave them in.

> > Those patches only touch the pulse/ subdir. 
> > 
> > The tree is freshly rebased against current alsa-plugins master.
> > 
> > May I ask you to make me the "semi-official" maintainer of this
> > driver? I.e. I'd like to be consulted (as in 'Signed-Off-by') before
> > any patches for it are merged?
> 
> Well, the patches can go in by any ALSA developers, so it can't be
> forced *always* through you.  But, I'll mail you pulse-related patches
> before reviewing and merging.

Thanks a lot!

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

      parent reply	other threads:[~2008-09-04 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 19:17 Pull request for alsa-plugins Lennart Poettering
2008-09-04  7:48 ` Takashi Iwai
2008-09-04 10:23   ` Colin Guthrie
2008-09-04 14:03   ` Lennart Poettering [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=20080904140339.GC31516@tango.0pointer.de \
    --to=mznyfn@0pointer.de \
    --cc=alsa-devel@alsa-project.org \
    /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