All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Scott Mollica <scott@exit-109.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM
Date: Mon, 27 Dec 2004 04:28:45 +0100	[thread overview]
Message-ID: <20041227032843.GF3002@stusta.de> (raw)
In-Reply-To: <20041224042234.10308.qmail@web51810.mail.yahoo.com>

On Thu, Dec 23, 2004 at 08:22:34PM -0800, Scott Mollica wrote:

> [1.] One line summary of the problem: 
> Problem 
> make utility exits with an Error 2 when making
> linux-2.6.9-final.  
>  
> [2.] Full description of the problem/report:
> make seems to choke in the
> "drivers/char/drm/gamma_drv.c" section during make
> (output from make is attached at bottom).
>...
>   CC [M]  drivers/char/drm/gamma_drv.o
> In file included from drivers/char/drm/gamma_drv.c:42:
> drivers/char/drm/gamma_context.h: In function
> `gamma_context_switch_complete':
> drivers/char/drm/gamma_context.h:193: error: structure
> has no member named `next_buffer'
>...
> make[3]: *** [drivers/char/drm/gamma_drv.o] Error 1
>...

It seems you answered "yes" to

  Code maturity level options
    Prompt for development and/or incomplete code/drivers

and "no" to

  Code maturity level options
    Prompt for development and/or incomplete code/drivers
      Select only drivers expected to compile cleanly

If you say "yes" to second question, you won't be able to select drivers 
that don't compile.

> Regards,
> Scott Mollica

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-12-27  3:28 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-24  4:22 PROBLEM Scott Mollica
2004-12-27  3:28 ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-27 22:38 Problem Michael Salman
2024-07-29 21:52 ` Problem brian m. carlson
2015-02-20  0:10 Problem Jeffrey O'Hara
2014-07-13  2:39 PROBLEM Michael P
2011-01-11 10:58 Problem Marco Sarzi Madidini
2011-01-11 13:37 ` Problem solarflow99
2011-01-11 15:38 ` Problem Frank Cox
2009-01-21 13:50 problem Csaba Dobo
2007-04-27  1:35 PROBLEM Thomas Kayser
2007-01-21  2:05 Problem Alessio Palmero Aprosio
2006-02-03 12:02 PROBLEM Badri Pillai
2004-12-20 12:10 problem nikolai
2004-12-20 12:45 ` problem Jesper Lund
2004-06-17 17:16 problem Admin
2003-12-19 18:10 PROBLEM Federico Freire
2003-12-19 18:25 ` PROBLEM Jean-Philippe Woot de Trixhe
2003-12-19 19:29   ` PROBLEM Jose Luis Domingo Lopez
2003-11-30  4:07 PROBLEM Mike Morrell
2003-11-30  6:05 ` PROBLEM Chris Ernst
2003-11-10  3:13 problem cemal
2003-11-10  3:17 ` problem Justin Zygmont
2003-10-21 13:39 PROBLEM laurent.miaille
2003-06-12 14:12 Problem Hector M Sanchez M
2003-05-09  1:26 problem useless
2003-03-17 21:07 Problem Pontus Falk
2003-03-17 21:43 ` Problem pa3gcu
2003-03-17 22:09   ` Problem Pontus Falk
2003-03-17 23:12     ` Problem Shane Deering
2003-03-18 15:50     ` Problem pa3gcu
2003-03-25  6:41       ` Problem Henk Remijn
2003-03-25 16:42         ` Problem bernard pidoux
2003-03-25 17:25           ` Problem Jarmo
2003-03-27 12:01             ` Problem bernard pidoux
2003-03-25 20:45           ` Problem pa3gcu
2003-03-26  0:46           ` Problem M Taylor
2003-03-13 21:40 Problem Smiler
2003-03-09 11:49 PROBLEM Kósa Ferenc
2003-03-09 12:55 ` PROBLEM John Bradford
2003-01-26  0:07 problem Mark Ryan
2003-01-26  1:41 ` problem Arnt Karlsen
2002-12-31 16:19 Problem Amar Lior
2002-12-31 17:38 ` Problem Hugh Dickins
2002-12-31 16:18 PROBLEM Amar Lior
2002-08-29 19:55 Problem Ryan White
2002-08-14 14:20 PROBLEM Bob Kruger
2001-09-11 23:16 Problem George Lloyd

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=20041227032843.GF3002@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott@exit-109.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.