linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: linux-next: Tree for December 12 (drm)
Date: Sun, 14 Dec 2008 11:21:13 -0800	[thread overview]
Message-ID: <200812141121.14400.jesse.barnes@intel.com> (raw)
In-Reply-To: <4943405A.4080009@xenotime.net>

On Friday, December 12, 2008 8:55 pm Randy Dunlap wrote:
> 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)

Looks like Dave pushed a fix for this by making DRM select the required I2C 
bits.  Dunno that or depends is preferred these days though...

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2008-12-14 19:21 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 ` linux-next: Tree for December 12 (drm) Randy Dunlap
2008-12-14 19:21   ` Jesse Barnes [this message]
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=200812141121.14400.jesse.barnes@intel.com \
    --to=jesse.barnes@intel.com \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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).