From: Martin Peres <martin.peres@ensi-bourges.fr>
To: bskeggs@redhat.com
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Zimny Lech <napohybelskurwysynom2010@gmail.com>,
Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: nouveau build failure (was Re: Linux 2.6.37-rc2)
Date: Wed, 17 Nov 2010 02:42:15 +0100 [thread overview]
Message-ID: <4CE332F7.2070805@ensi-bourges.fr> (raw)
In-Reply-To: <1289941098.20058.1.camel@nisroch>
Le 16/11/2010 21:58, Ben Skeggs a écrit :
> On Tue, 2010-11-16 at 12:50 -0800, Randy Dunlap wrote:
>> On Tue, 16 Nov 2010 12:45:43 -0800 Linus Torvalds wrote:
>>
>>> Looks like commit 34e9d85a1aae ("drm/nouveau: Add temperature support
>>> (vbios parsing, readings, hwmon)") didn't make things properly
>>> dependent on CONFIG_HWMON (or do the appropriate "select HWMON" or
>>> whatever).
>>>
>>> Added some collection of hopefully more relevant people to the discussion..
>>>
>>> Linus
>>
>> This build error was reported for linux-next on 2010.1011 and 2010.1025,
>> with no replies.
>>
>> Some process fix would be nice to see.
> It's actually been fixed in the nouveau tree, I have to go through and
> get fixes out of it and send them to Dave.
>
> Ben.
Thanks Ben, I should have checked my fix actually went in David's
drm-fixes branch. I'll try to be more vigilent on this in the future.
Martin
next prev parent reply other threads:[~2010-11-17 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 20:45 nouveau build failure (was Re: Linux 2.6.37-rc2) Linus Torvalds
2010-11-16 20:50 ` Randy Dunlap
2010-11-16 20:58 ` Ben Skeggs
2010-11-16 21:20 ` Zimny Lech
2010-11-17 1:42 ` Martin Peres [this message]
2010-11-17 1:43 ` Ben Skeggs
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=4CE332F7.2070805@ensi-bourges.fr \
--to=martin.peres@ensi-bourges.fr \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
/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