All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jenny TC <jenny.tc@intel.com>
Cc: alsa-devel@alsa-project.org,
	Jairaj Arava <jairaj.arava@intel.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Harsha Priya <harshapriya.n@intel.com>,
	Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Matthias Kaehlcke <mka@chromium.org>,
	Sathyanarayana Nujella <sathyanarayana.nujella@intel.com>
Subject: Re: [PATCH 1/2] ASoC: dmic: Enable ACPI device entry
Date: Tue, 2 Oct 2018 16:00:57 +0100	[thread overview]
Message-ID: <20181002150057.GC6338@sirena.org.uk> (raw)
In-Reply-To: <1538459851-17066-2-git-send-email-jenny.tc@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 333 bytes --]

On Tue, Oct 02, 2018 at 11:27:30AM +0530, Jenny TC wrote:

> +#ifdef CONFIG_ACPI
> +static const struct acpi_device_id dmic_acpi_match[] = {
> +	{ "DMIC", 0 },
> +	{},
> +};
> +MODULE_DEVICE_TABLE(acpi, dmic_acpi_match);
> +#endif

This doesn't look like a standards conforming ACPI identifier, I thought
they were all 8 characters?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2018-10-02 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02  5:57 [PATCH 0/2] Introduce dmic mode switch delay parameter Jenny TC
2018-10-02  5:57 ` [PATCH 1/2] ASoC: dmic: Enable ACPI device entry Jenny TC
2018-10-02 15:00   ` Mark Brown [this message]
2018-10-02 17:12   ` Matthias Kaehlcke
2018-10-02  5:57 ` [PATCH 2/2] ASoC: dmic: Introduce mode switch delay Jenny TC
2018-10-22  3:42 ` [PATCH 0/2] Introduce dmic mode switch delay parameter Pierre-Louis Bossart
2018-10-22 14:31   ` Pierre-Louis Bossart
2018-10-23 17:11     ` Tc, Jenny
2018-10-23 18:22       ` Pierre-Louis Bossart
2018-10-24 13:40         ` Mark Brown
2018-10-24 13:35       ` Mark Brown
2018-10-25 16:08   ` Vinod Koul

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=20181002150057.GC6338@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=harshapriya.n@intel.com \
    --cc=jairaj.arava@intel.com \
    --cc=jenny.tc@intel.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=mka@chromium.org \
    --cc=sathyanarayana.nujella@intel.com \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.