public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sudeep Dutt <sudeep.dutt@intel.com>,
	Ashutosh Dixit <ashutosh.dixit@intel.com>,
	Caz Yokoyama <Caz.Yokoyama@intel.com>,
	Dasaratharaman Chandramouli 
	<dasaratharaman.chandramouli@intel.com>,
	Nikhil Rao <nikhil.rao@intel.com>,
	Harshavardhan R Kharche <harshavardhan.r.kharche@intel.com>
Subject: Re: linux-next: build failure after merge of the final tree (char-misc tree related)
Date: Fri, 27 Sep 2013 18:04:44 -0700	[thread overview]
Message-ID: <20130928010444.GC22939@kroah.com> (raw)
In-Reply-To: <20130927184804.ddb460377bcd3fb35f8b41d2@canb.auug.org.au>

On Fri, Sep 27, 2013 at 06:48:04PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> drivers/misc/mic/card/mic_x100.c: In function 'mic_init':
> drivers/misc/mic/card/mic_x100.c:215:9: error: implicit declaration of function 'cpu_data' [-Werror=implicit-function-declaration]
>   struct cpuinfo_x86 *c = &cpu_data(0);
>          ^

<snip>

Should now be fixed, thanks.

greg k-h

  reply	other threads:[~2013-09-28  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27  8:48 linux-next: build failure after merge of the final tree (char-misc tree related) Stephen Rothwell
2013-09-28  1:04 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-03  8:39 Stephen Rothwell
2014-03-03  8:45 Stephen Rothwell

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=20130928010444.GC22939@kroah.com \
    --to=greg@kroah.com \
    --cc=Caz.Yokoyama@intel.com \
    --cc=arnd@arndb.de \
    --cc=ashutosh.dixit@intel.com \
    --cc=dasaratharaman.chandramouli@intel.com \
    --cc=harshavardhan.r.kharche@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nikhil.rao@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sudeep.dutt@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