From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
jesse.barnes@intel.com, airlied@linux.ie
Subject: Re: linux-next: Tree for December 12 (drm)
Date: Fri, 12 Dec 2008 20:55:54 -0800 [thread overview]
Message-ID: <4943405A.4080009@xenotime.net> (raw)
In-Reply-To: <20081212185654.0af8b4a1.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20081211:
>
> Undropped tree:
> drm
oops ^^^
When I2C=n, and drm is built-in or modular, this build error
happens:
(drm built-in:)
build-r7079.out:(.text+0x47e5f): undefined reference to `i2c_transfer'
7080 same
7086 same
7089 same
(from gpu/drm/drm_edid.c)
(drm modular:)
build-r7103.out:ERROR: "i2c_transfer" [drivers/gpu/drm/drm.ko] undefined!
(from gpu/drm/drm_edid.c)
~Randy
next prev parent reply other threads:[~2008-12-13 4:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 7:56 linux-next: Tree for December 12 Stephen Rothwell
2008-12-13 4:55 ` Randy Dunlap [this message]
2008-12-14 19:21 ` linux-next: Tree for December 12 (drm) Jesse Barnes
2008-12-14 5:26 ` linux-next: Tree for December 12 (netdev ops) Randy Dunlap
2008-12-15 23:07 ` David Miller
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=4943405A.4080009@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=airlied@linux.ie \
--cc=jesse.barnes@intel.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;
as well as URLs for NNTP newsgroup(s).