linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: hermann <brummer-@web.de>
Cc: linux-rt-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Grant Likely <grant.likely@secretlab.ca>,
	devicetree-discuss@lists.ozlabs.org,
	Rusty Russell <rusty@rustcorp.com.au>,
	lguest@lists.ozlabs.org
Subject: Re: [PATCH] Various fixups from first bug reports
Date: Fri, 22 Jul 2011 08:57:11 +0200	[thread overview]
Message-ID: <20110722065711.GD16561@pengutronix.de> (raw)
In-Reply-To: <1311313414.2940.8.camel@box>

Hello,

(These two issues occured on 3.0-rc7-rt0, I think they apply to
mainline, too.)

On Fri, Jul 22, 2011 at 07:43:34AM +0200, hermann wrote:
> well, I run into 2 ops, witch, I guess not related to the rt patch.
> 
> first one was with CONFIG_SENSORS_LTC4245, module build stage 2 failed
> with undefined reference to of_find_property
of_find_property isn't exported to modules. Maybe of_get_property should
be used? Should of_find_property be static then? Alternatively export
of_find_property, too. Grant?

> second was with CONFIG_LGUEST_GUEST enabled, module build stage 2 failed
> with Documentation/lguest not found
Hmm, there is Documentation/virtual/lguest. Didn't find where
Documentation/lguest is used from a quick look. Rusty?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-07-22  6:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 16:22 [ANNOUNCE] 3.0-rc7-rt0 hermann
2011-07-21 17:35 ` Thomas Gleixner
2011-07-21 17:43   ` Thomas Gleixner
2011-07-21 18:33     ` hermann
2011-07-23  4:08     ` [ANNOUNCE] 3.0-rt1 hermann
2011-07-23  7:37       ` Thomas Gleixner
2011-07-21 18:28   ` [ANNOUNCE] 3.0-rc7-rt0 andi
2011-07-21 18:40     ` hermann
2011-07-21 19:57   ` [PATCH] Various fixups from first bug reports Uwe Kleine-König
2011-07-22  5:43     ` hermann
2011-07-22  6:57       ` Uwe Kleine-König [this message]
2011-07-22  7:40         ` hermann
2011-07-22 10:06           ` Trulan Martin
2011-07-22 11:04         ` Rusty Russell
2011-07-22 19:20           ` Uwe Kleine-König
2011-07-23  3:17             ` hermann
2011-07-23  9:57               ` Robin Gareus
     [not found]                 ` <4E2A9B18.6030000-+VlDMftONaMdnm+yROfE0A@public.gmane.org>
2011-07-23 14:19                   ` hermann
2011-07-23 14:33                     ` Robin Gareus
2011-07-23 15:21                       ` hermann
2011-07-23 18:53                     ` Uwe Kleine-König

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=20110722065711.GD16561@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=brummer-@web.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=lguest@lists.ozlabs.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    /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).