All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
	kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org
Subject: Re: [asoc:topic/max9867 2/4] sound/soc/codecs/max9867.c:294:11: error: 'component' undeclared; did you mean 'complete'?
Date: Thu, 1 Mar 2018 22:34:37 +0100	[thread overview]
Message-ID: <20180301213436.GB3833@lenoch> (raw)
In-Reply-To: <20180301200430.GA23704@sirena.org.uk>

On Thu, Mar 01, 2018 at 08:04:30PM +0000, Mark Brown wrote:
> On Thu, Mar 01, 2018 at 09:01:56PM +0100, Ladislav Michl wrote:
> > On Fri, Mar 02, 2018 at 03:45:16AM +0800, kbuild test robot wrote:
> 
> > >    sound/soc/codecs/max9867.c:294:11: note: each undeclared identifier is reported only once for each function it appears in
> 
> > your topic/max9867 seems to be 4.16-rc1 based, while patch was tested
> > in today's -next. Fixing it for 4.16-rc1 would mean it fails to compile
> > once you merge topic branches.
> 
> > What am I supposed to do here?
> 
> Which other commits in my tree does this depend on?

91880a6b6ba3 ("ASoC: wm9867: replace codec to component")
Note, we have naming problem here...

  reply	other threads:[~2018-03-01 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 19:45 [asoc:topic/max9867 2/4] sound/soc/codecs/max9867.c:294:11: error: 'component' undeclared; did you mean 'complete'? kbuild test robot
2018-03-01 20:01 ` Ladislav Michl
2018-03-01 20:04   ` Mark Brown
2018-03-01 21:34     ` Ladislav Michl [this message]
2018-03-01 21:36       ` Mark Brown

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=20180301213436.GB3833@lenoch \
    --to=ladis@linux-mips.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    /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.