archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <>
To: Thierry Reding <>,,
Cc: Mark Brown <>,
	Srinivas Pandruvada <>,
	Jacob Pan <>,
	"Rafael J. Wysocki" <>
Subject: Re: linux-next: Tree for Oct 25 (powercap_sys.c)
Date: Fri, 25 Oct 2013 12:46:29 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 10/25/13 08:03, Thierry Reding wrote:
> Hi all,
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>         git://
> A next-20131025 tag is also provided for convenience.
> One new trivial conflicts and a new build failure caused by an incorrect
> use of the genpool allocator.
> Upon a request from Olof Johansson I've only included fixes for build
> breakage as a result of interactions between the various trees. But
> since I've fixed many of the other build failures already, I've pushed
> those to a separate tag (next-20131025-fixes). That builds fine on x86
> 32-bit and 64-bit allmodconfigs as well as ARM and x86 default
> configurations. Most of the PowerPC build errors have also been fixed.

on i386:

drivers/powercap/powercap_sys.c:484:2: error: unknown field 'dev_attrs' specified in initializer
drivers/powercap/powercap_sys.c:484:2: warning: initialization from incompatible pointer type [enabled by default]
drivers/powercap/powercap_sys.c:484:2: warning: (near initialization for 'powercap_class.suspend') [enabled by default]


  parent reply	other threads:[~2013-10-25 19:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 15:03 linux-next: Tree for Oct 25 Thierry Reding
2013-10-25 15:03 ` linux-next: manual merge of the block tree Thierry Reding
2013-10-25 19:46 ` Randy Dunlap [this message]
2013-10-25 22:17   ` linux-next: Tree for Oct 25 (powercap_sys.c) Srinivas Pandruvada
2013-10-25 22:30     ` Srinivas Pandruvada
2013-10-25 21:01 ` linux-next: Tree for Oct 25 Guenter Roeck
2013-10-25 21:12 ` linux-next: Tree for Oct 25 (of_gpio.h) Randy Dunlap
2013-10-25 22:31 ` linux-next: Tree for Oct 25 Randy Dunlap
2013-10-26 16:59   ` Mark Brown
2013-10-28  8:01   ` Thierry Reding
2013-10-28 16:53     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).