All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 35441] New: header files (at least nouveau_device.h and nouveau_grojb.h) missing from git
Date: Fri, 18 Mar 2011 20:43:27 -0700 (PDT)	[thread overview]
Message-ID: <bug-35441-8800@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=35441

           Summary: header files (at least nouveau_device.h and
                    nouveau_grojb.h) missing from git
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: rwhite-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org


The current git repository as of this date is missing at least two header files
referenced by src/mesa/drivers/dri/nouveau/nouveau_driver.h

The file nouveau_device.h is missing and when I just experimentally commented
that out then nouveau_gobj.h cropped up missing so I stopped.

All the other header files in the same block of includes that I could locate
are all apparently local to this directory. They are also all local includes
(e.g. in "" not <> quotes) so I figure they are all from here.

spot checking I think

nouveau_device.h, nouveau_grobj.h, nouveau_channel.h, and nouveau_notifier.h
and any .c files they front for are suspiciously missing or live somewhere
inobvious to me.

This was first observed about two weeks ago but I didn't realize this was the
right place to report it. /doh.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-03-19  3:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19  3:43 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-35441-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-03-20  7:15   ` [Bug 35441] header files (at least nouveau_device.h and nouveau_grojb.h) missing from git bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-24  9:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-24  9:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-24 18:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-25  8:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-25  8:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-27 11:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-27 19:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-29 16:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-29 16:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-30 10:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-30 10:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-13  7:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-14 17:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-14 18:01   ` [Bug 35441] [PATCH] Mesa does not find nouveau include files with --enable-shared-dricore bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-35441-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.