From: Tobias Schneider <tobsnyder@gmx.de>
To: Daniel Mack <daniel@caiaq.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA Control Questions (atomicity, error handling)
Date: Fri, 04 Dec 2009 13:02:35 +0100 [thread overview]
Message-ID: <4B18FA5B.8080600@gmx.de> (raw)
In-Reply-To: <20091204113434.GR14091@buzzloop.caiaq.de>
okay, so it was my fault, thanks!
> One more thing: in case you intend to bring your code mainline, please
> run scripts/checkpatch.pl on the patches before you submit. The sniplet
> you posted has a number of style issues that should be fixed. In
> particular, pay attention to indentation, comment style and parenthesis
> positions - checkpatch.pl will help pointing out most if them.
>
> Daniel
is there also any document (something like ALSA coding style guide)?
so far,
thanks a lot
Tobias
next prev parent reply other threads:[~2009-12-04 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 18:30 ALSA Control Questions Tobias Schneider
2009-12-03 19:50 ` Daniel Mack
2009-12-04 9:31 ` ALSA Control Questions (atomicity, error handling) Tobias Schneider
2009-12-04 11:27 ` Daniel Mack
2009-12-04 11:34 ` Daniel Mack
2009-12-04 12:02 ` Tobias Schneider [this message]
2009-12-04 12:06 ` Daniel Mack
2009-12-04 12:33 ` Clemens Ladisch
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=4B18FA5B.8080600@gmx.de \
--to=tobsnyder@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@caiaq.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