All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lu Guanqun <guanqun.lu@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>, "gregkh@suse.de`" <gregkh@suse.de`>,
	ALSA <alsa-devel@alsa-project.org>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] sst: fix compile error
Date: Thu, 7 Apr 2011 14:44:20 +0800	[thread overview]
Message-ID: <20110407064420.GC8484@qtel.sh.intel.com> (raw)
In-Reply-To: <20110407062717.GA14519@opensource.wolfsonmicro.com>

On Thu, Apr 07, 2011 at 02:27:18PM +0800, Mark Brown wrote:
> On Thu, Apr 07, 2011 at 10:18:13AM +0800, Lu Guanqun wrote:
> > Add several include files to fix the below compile error.
> > 
> > drivers/staging/intel_sst/intelmid.c: In function ‘snd_intelmad_sst_register’:
> > drivers/staging/intel_sst/intelmid.c:612:2: error: ‘sst_drv_ctx’ undeclared (first use in this function)
> > drivers/staging/intel_sst/intelmid.c:612:2: note: each undeclared identifier is reported only once for each function it appears in
> > 
> > Signed-off-by: Lu Guanqun <guanqun.lu@intel.com>
> 
> Is this needed in 2.6.39?  Greg, I'm happy to take this through ASoC if
> you're OK with that.

Hi Mark,

This isn't needed for 2.6.39.

This compile error is actually caused by my fault, see below commit.

commit 0ed625b2f2751c249417bd28694e37ef48eb5fbb
Author: Lu Guanqun <guanqun.lu@intel.com>
Date:   Wed Apr 6 10:20:42 2011 +0800

    sst: make register_sst_card more self-contained
    
    register_sst_card is used in ASoC code with field `scard_ops` being NULL.
    Without this patch, there will be NULL dereference.
    
    Signed-off-by: Lu Guanqun <guanqun.lu@intel.com>
    Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

And this commit is only in your branch for-2.6.40. I failed to add
CONFIG_INTELMID=y in my previous test, so this error is hidden.

> 
> > ---
> >  drivers/staging/intel_sst/intelmid.c |    3 +++
> >  1 files changed, 3 insertions(+), 0 deletions(-)
> > 
> > diff --git a/drivers/staging/intel_sst/intelmid.c b/drivers/staging/intel_sst/intelmid.c
> > index 32ded14..bbda30f 100644
> > --- a/drivers/staging/intel_sst/intelmid.c
> > +++ b/drivers/staging/intel_sst/intelmid.c
> > @@ -37,8 +37,11 @@
> >  #include <sound/pcm_params.h>
> >  #include <sound/initval.h>
> >  #include <linux/gpio.h>
> > +#include <linux/firmware.h>
> >  #include "intel_sst.h"
> >  #include "intel_sst_ioctl.h"
> > +#include "intel_sst_fw_ipc.h"
> > +#include "intel_sst_common.h"
> >  #include "intelmid_snd_control.h"
> >  #include "intelmid_adc_control.h"
> >  #include "intelmid.h"
> > 

-- 
guanqun
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2011-04-07  6:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07  2:18 [PATCH] sst: fix compile error Lu Guanqun
2011-04-07  6:27 ` Mark Brown
2011-04-07  6:44   ` Lu Guanqun [this message]
2011-04-07  7:50     ` Mark Brown
2011-04-07  8:00       ` Lu Guanqun
2011-04-08  0:21 ` Mark Brown
2011-04-08  0:42   ` Lu Guanqun

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=20110407064420.GC8484@qtel.sh.intel.com \
    --to=guanqun.lu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gregkh@suse.de` \
    --cc=lrg@slimlogic.co.uk \
    --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 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.