From: changjoon.lee@lge.com
To: tiwai@suse.de
Cc: alsa-devel@alsa-project.org, linux@endlessm.com,
linux-kernel@vger.kernel.org,
ChangJoon Lee <changjoon.lee@lge.com>
Subject: [PATCH 0/1] Documentation update
Date: Tue, 12 May 2020 18:05:46 +0900 [thread overview]
Message-ID: <20200512090547.76991-1-changjoon.lee@lge.com> (raw)
From: ChangJoon Lee <changjoon.lee@lge.com>
ChangJoon Lee (1):
Updated negative return values for documentation update.
src/pcm/pcm.c | 57 ++++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 54 insertions(+), 3 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-12 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 9:05 changjoon.lee [this message]
2020-05-12 9:05 ` [PATCH 1/1] Updated negative return values for documentation update changjoon.lee
2020-05-14 2:47 ` CJ Lee
2020-05-14 7:54 ` Takashi Iwai
2020-05-14 9:07 [PATCH 0/1] Documentation update changjoon.lee
2020-05-14 9:20 ` Takashi Iwai
2020-05-14 9:22 ` 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=20200512090547.76991-1-changjoon.lee@lge.com \
--to=changjoon.lee@lge.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).