Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kirill Smelkov <kirr@mns.spb.ru>
Cc: alsa-devel@alsa-project.org
Subject: Re: [patch] writing-an-alsa-driver typo fixes
Date: Thu, 13 Jan 2005 18:29:34 +0100	[thread overview]
Message-ID: <s5hllaxi6f5.wl@alsa2.suse.de> (raw)
In-Reply-To: <200501121832.23003.kirr@mns.spb.ru>

At Wed, 12 Jan 2005 18:32:22 +0300,
Kirill Smelkov wrote:
> 
> Hello,
> 
> While reading the writing-an-alsa-driver document i've discovered a few typos,
> some obsolete text fragments.
> 
> Also i fixed some referenced file names and a few comments

Thanks, both patches are applied to CVS.


Takashi


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

      reply	other threads:[~2005-01-13 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 15:32 [patch] writing-an-alsa-driver typo fixes Kirill Smelkov
2005-01-13 17:29 ` Takashi Iwai [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=s5hllaxi6f5.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kirr@mns.spb.ru \
    /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