From: Len Brown <lenb@kernel.org>
To: Crane Cai <crane.cai@amd.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: acpi tree build failure
Date: Sun, 27 Sep 2009 03:54:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0909270353100.16783@localhost.localdomain> (raw)
In-Reply-To: <20090927012716.GB10173@crane-desktop>
> > > drivers/i2c/busses/i2c-scmi.c: In function 'acpi_smbus_cmi_add':
> > > drivers/i2c/busses/i2c-scmi.c:374: error: implicit declaration of function 'acpi_device_uid'
> > > drivers/i2c/busses/i2c-scmi.c:374: warning: format '%s' expects type 'char *', but argument 5 has type 'int'
> > >
> > > Caused by commit 6622d8cee73a26bce958484065c8f0e704911a62 ("ACPI: remove
> > > acpi_device_uid() and related stuff") interacting with commit
> > > dc9854212e0d7318d7133697906d98b78f3088b6 ("i2c: Add driver for SMBus
> > > Control Method Interface") recently added to Linus' tree.
> > >
> > > I have used the version of the acpi tree from next-20090925 for today.
> >
> > I think we should use the following patch to remove the usage of
> > acpi_device_uid(). Crane, do you agree, or is there some special
> > reason you need it here?
> I agree.
Thanks Crane, upstream now includes Bjorn's patch.
-Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-09-27 7:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 2:15 linux-next: acpi tree build failure Stephen Rothwell
2009-09-26 3:11 ` Bjorn Helgaas
2009-09-27 1:27 ` Crane Cai
2009-09-27 7:54 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-14 1:20 Stephen Rothwell
2009-12-14 19:20 ` Bjorn Helgaas
2009-12-15 4:57 ` Bjorn Helgaas
2009-12-15 22:37 ` Len Brown
2009-12-15 23:28 ` Stephen Rothwell
2009-12-16 2:28 ` Stephen Rothwell
2009-09-01 2:57 Stephen Rothwell
2009-09-07 13:46 ` Stephen Rothwell
2009-09-08 0:47 ` Zhang Rui
2009-09-09 4:02 ` Len Brown
2009-09-09 5:45 ` Stephen Rothwell
2009-06-30 3:16 Stephen Rothwell
2009-07-06 6:18 ` Stephen Rothwell
2009-07-07 3:17 ` Len Brown
2009-07-07 3:53 ` Stephen Rothwell
2009-04-24 4:46 Stephen Rothwell
2009-04-24 15:15 ` Len Brown
2009-03-18 0:57 Stephen Rothwell
2009-03-18 1:09 ` Lin Ming
2009-03-18 3:27 ` Stephen Rothwell
2009-03-27 20:49 ` Len Brown
2009-02-24 4:37 Stephen Rothwell
2009-03-03 1:47 ` Stephen Rothwell
2009-03-16 5:10 ` Stephen Rothwell
2009-03-27 20:58 ` Len Brown
2009-02-02 2:22 Stephen Rothwell
2009-02-05 2:13 ` Stephen Rothwell
2009-02-05 5:00 ` Greg KH
2009-02-07 4:06 ` Len Brown
2009-02-07 5:32 ` Greg KH
2008-10-15 5:08 Stephen Rothwell
2008-10-15 5:15 ` Shaohua Li
2008-10-15 4:51 Stephen Rothwell
2008-08-12 3:16 Stephen Rothwell
2008-08-12 7:06 ` Andi Kleen
2008-08-12 20:07 ` Carlos Corbacho
2008-08-12 21:29 ` Carlos Corbacho
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=alpine.LFD.2.00.0909270353100.16783@localhost.localdomain \
--to=lenb@kernel.org \
--cc=bjorn.helgaas@hp.com \
--cc=crane.cai@amd.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox