From: Wolfram Sang <w.sang@pengutronix.de>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>, ebiederm@xmission.com
Subject: Re: 2.6.34-rc: key ffff8801fefc0310 not in .data!
Date: Tue, 6 Apr 2010 10:19:12 +0200 [thread overview]
Message-ID: <20100406081912.GC5102@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.01.1004052344210.29272@bogon.housecafe.de>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On Mon, Apr 05, 2010 at 11:57:19PM -0700, Christian Kujau wrote:
> Hi,
>
> similar messages have been reported for CONFIG_MICROCODE [0] and
> CONFIG_THERMAL [1], this one is for something else, I guess:
Should have been fixed by ebd09ec93c90c8ec571d7e166832fb1fc705bf5e
(which came after -rc3).
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-04-06 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 6:57 Christian Kujau
2010-04-06 8:19 ` Wolfram Sang [this message]
2010-04-06 8:35 ` Christian Kujau
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=20100406081912.GC5102@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.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
all inboxes | Powered by JetHome®