All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: tiwai@suse.de, patches.audio@intel.com,
	alsa-devel@alsa-project.org, broonie@kernel.org,
	liam.r.girdwood@linux.intel.com
Subject: Re: [PATCH] ASoC: Intel: mfld: allow mfld machine to be build
Date: Wed, 15 Nov 2017 10:20:51 -0600	[thread overview]
Message-ID: <aff81d5e-4894-67d5-b044-342dea4871fe@linux.intel.com> (raw)
In-Reply-To: <20171115152534.GJ3187@localhost>

On 11/15/17 9:25 AM, Vinod Koul wrote:
> On Wed, Nov 15, 2017 at 08:41:18AM -0600, Pierre-Louis Bossart wrote:
>> On 11/15/17 4:52 AM, Vinod Koul wrote:
>>> Commit b97169da0699: ("ASoC: Intel: create atom folder and move atom
>>> platform files in") missed adding Kconfig and Makefile support for
>>> MFLD machine driver, so add it while alos fixing the relative patch to
>>> codec header
>>
>> Does anyone test this code? I don't think anyone on the Intel side has a
>> working platform any longer...
> 
> That is good question, we had boards for these but not sure if this is
> needed. This was not compiling and noone noticed, so I dont mind removing
> these bits.
> 
> Any objections..

I saw those configs were not used and I thought it was deprecated on 
purpose...

  reply	other threads:[~2017-11-16 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 10:52 [PATCH] ASoC: Intel: mfld: allow mfld machine to be build Vinod Koul
     [not found] ` <2fc42908-631d-364f-c531-c05f077eceb4@linux.intel.com>
2017-11-15 15:25   ` Vinod Koul
2017-11-15 16:20     ` Pierre-Louis Bossart [this message]
2017-11-17 11:42       ` 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=aff81d5e-4894-67d5-b044-342dea4871fe@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@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 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.