All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: ego@linux.vnet.ibm.com
Cc: svaidy@linux.vnet.ibm.com, preeti@linux.vnet.ibm.com,
	srivatsa.bhat@linux.vnet.ibm.com, linux-next@vger.kernel.org,
	rafael.j.wysocki@intel.com
Subject: [next] powernv: cpufreq driver build fail for non-SMP
Date: Tue, 15 Apr 2014 10:11:11 -0400	[thread overview]
Message-ID: <20140415141111.GA28352@windriver.com> (raw)

Hi all,

This new driver is causing build fails on linux-next for non-SMP.

http://kisskb.ellerman.id.au/kisskb/buildresult/10911507/

I didn't bisect since there are only two commits in total.  :)

Looks like some header foo where <linux/smp.h> is not getting <asm/smp.h>

Paul.

             reply	other threads:[~2014-04-15 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 14:11 Paul Gortmaker [this message]
2014-04-16  5:48 ` [PATCH] cpufreq, powernv: Fix build failure on UP Srivatsa S. Bhat
2014-04-16  5:55   ` Viresh Kumar
2014-04-16  6:01     ` Srivatsa S. Bhat

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=20140415141111.GA28352@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=ego@linux.vnet.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=preeti@linux.vnet.ibm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=svaidy@linux.vnet.ibm.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.