From: Takashi Iwai <tiwai@suse.de>
To: Colin King <colin.king@canonical.com>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound/oss/pss: fix spelling mistake: "compoents" -> "components"
Date: Thu, 24 Aug 2017 09:13:17 +0200 [thread overview]
Message-ID: <s5h4lsxv3oy.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170823224934.12385-1-colin.king@canonical.com>
On Thu, 24 Aug 2017 00:49:34 +0200,
Colin King wrote:
>
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in MODULE_PARM_DESC text
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
The OSS code is already dead (kconfig disabled) and going to be
removed sooner or later, so let's leave as is.
thanks,
Takashi
prev parent reply other threads:[~2017-08-24 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 22:49 [PATCH] sound/oss/pss: fix spelling mistake: "compoents" -> "components" Colin King
2017-08-24 7:13 ` 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=s5h4lsxv3oy.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=colin.king@canonical.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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