From: Joe Perches <joe@perches.com>
To: Mark Brown <broonie@kernel.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org,
liam.r.girdwood@linux.intel.com, linux-kernel@vger.kernel.org,
perex@perex.cz, pierre-louis.bossart@linux.intel.com,
tiwai@suse.com, yang.jie@linux.intel.com
Subject: Re: Applied "ASoC: Intel: Fix some acpi vs apci typo in somme comments" to the asoc tree
Date: Thu, 25 Jul 2019 06:44:55 -0700 [thread overview]
Message-ID: <8179fff75f82ac49aaa0c5feb17b53be55f9f2c5.camel@perches.com> (raw)
In-Reply-To: <20190725131925.D36082742B5F@ypsilon.sirena.org.uk>
On Thu, 2019-07-25 at 14:19 +0100, Mark Brown wrote:
> The patch
>
> ASoC: Intel: Fix some acpi vs apci typo in somme comments
[]
> diff --git a/sound/soc/intel/common/soc-acpi-intel-bxt-match.c b/sound/soc/intel/common/soc-acpi-intel-bxt-match.c
[]
> @@ -1,6 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0
> /*
> - * soc-apci-intel-bxt-match.c - tables and support for BXT ACPI enumeration.
> + * soc-acpi-intel-bxt-match.c - tables and support for BXT ACPI enumeration.
Generally, using the current filename in a comment has little value.
This might as well be
* tables and support for BXT ACPI enumeration
etc...
prev parent reply other threads:[~2019-07-25 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 5:35 [PATCH] ASoC: Intel: Fix some acpi vs apci typo in somme comments Christophe JAILLET
2019-07-25 13:07 ` Pierre-Louis Bossart
2019-07-25 13:19 ` Applied "ASoC: Intel: Fix some acpi vs apci typo in somme comments" to the asoc tree Mark Brown
2019-07-25 13:44 ` Joe Perches [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=8179fff75f82ac49aaa0c5feb17b53be55f9f2c5.camel@perches.com \
--to=joe@perches.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.com \
/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).