From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Woodhouse <dwmw2@infradead.org>,
Andres Salomon <dilinger@collabora.co.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 4 (olpc_battery)
Date: Mon, 9 Aug 2010 09:39:25 -0700 [thread overview]
Message-ID: <20100809093925.1ff3dc11.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100804094755.e0377eb0.randy.dunlap@oracle.com>
On Wed, 4 Aug 2010 09:47:55 -0700 Randy Dunlap wrote:
> On Wed, 4 Aug 2010 15:10:35 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > As the merge window is open, please do not add 2.6.27 material to your
> > linux-next included trees until after 2.6.36-rc1.
> >
> > Changes since 20100803:
>
>
> drivers/power/olpc_battery.c:387: error: unknown field 'owner' specified in initializer
> drivers/power/olpc_battery.c:387: warning: excess elements in struct initializer
> drivers/power/olpc_battery.c:387: warning: (near initialization for 'olpc_bat_eeprom.attr')
>
>
> The .owner field has been dropped from the attr struct.
Build still fails in linux-next 20100809.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-09 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 5:10 linux-next: Tree for August 4 Stephen Rothwell
2010-08-04 16:47 ` linux-next: Tree for August 4 (olpc_battery) Randy Dunlap
2010-08-09 16:39 ` Randy Dunlap [this message]
2010-08-09 17:17 ` David Woodhouse
2010-08-09 17:25 ` Anton Vorontsov
2010-08-04 17:16 ` [PATCH -next] ceph: rbd depends on BLOCK Randy Dunlap
[not found] ` <20100804222350.GA2220@phenom.dumpdata.com>
2010-08-04 22:24 ` linux-next: Tree for August 4, add a new git tree please? Konrad Rzeszutek Wilk
2010-08-05 0:30 ` Stephen Rothwell
2010-08-05 14:37 ` Konrad Rzeszutek Wilk
2010-08-05 14:41 ` 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=20100809093925.1ff3dc11.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dilinger@collabora.co.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.