dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Vesely <jan.vesely@rutgers.edu>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH libdrm 9/8] Remove drmSetDebugMsgFunction and related infrastructure
Date: Fri, 20 Mar 2015 17:42:27 -0400	[thread overview]
Message-ID: <1426887747.3949.32.camel@rutgers.edu> (raw)
In-Reply-To: <CACvgo50UZOiuHKMMM_ZVC+jP8TAaCbAAsVWZ9XaWB-Ui0u_DeA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1163 bytes --]

On Fri, 2015-03-20 at 21:06 +0000, Emil Velikov wrote:
> On 18 March 2015 at 18:37, Jan Vesely <jan.vesely@rutgers.edu> wrote:
> > Not used anywhere
> >
> Some information from my digging around:
> 
> Function was added with commit 79038751ffe(libdrm: add support for
> server side functionality in libdrm).
> It's not referenced even once in the history of the following projects
>  - xserver
>  - plymouth
>  - mesa
>  - xf86-video-ati
>   -xf86-video-freedreno
>  - xf86-video-i128
>  - xf86-video-i740
>  - xf86-video-intel
>  - xf86-video-mach64
>  - xf86-video-mga
>  - xf86-video-nouveau
>  - xf86-video-r128
>  - xf86-video-tdfx
>  - xf86-video-savage
>  - xf86-video-sis
>  - xf86-video-via
> 
> So I'm pretty confident that we're safe to nuke it. The above ddx list
> should consist of all the drivers/hardware that was ever officially
> supported by drm - from dri1 era until now.
> 
> Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>

thanks for checking those. I still don;t have a clear idea which
projects actually use libdrm (other than mesa)

jan

> 
> -Emil

-- 
Jan Vesely <jan.vesely@rutgers.edu>

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-03-20 21:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 18:07 [PATCH libdrm 0/8] Warnings fixes Jan Vesely
2015-02-27 18:07 ` [PATCH libdrm 1/8] Add static qualifier to local functions Jan Vesely
2015-03-13 23:07   ` Emil Velikov
2015-03-14  0:08     ` Jan Vesely
2015-03-14 13:12       ` Emil Velikov
2015-03-15 18:09         ` [PATCH libdrm v2 " Jan Vesely
2015-03-16 21:44           ` Emil Velikov
2015-02-27 18:07 ` [PATCH libdrm 2/8] tests: String literals are const char * Jan Vesely
2015-02-27 18:07 ` [PATCH libdrm 3/8] Fix type-limits, pointer-arith and sign-compare warnings Jan Vesely
2015-02-27 18:07 ` [PATCH libdrm 4/8] xf86drmSL: Fix neighbour printing Jan Vesely
2015-03-15 18:31   ` Jan Vesely
2015-03-20 17:38   ` Emil Velikov
2015-03-20 18:01     ` Jan Vesely
2015-03-20 22:00       ` Jan Vesely
2015-02-27 18:07 ` [PATCH libdrm 5/8] Fix aliasing and switch-enum warnings Jan Vesely
2015-03-13 23:15   ` Emil Velikov
2015-02-27 18:07 ` [PATCH libdrm 6/8] dristat: Handle DRM_CONSISTENT Jan Vesely
2015-02-27 18:07 ` [PATCH libdrm 7/8] Fix unused, and unused-but-set variables warnings Jan Vesely
2015-03-13 22:56   ` Emil Velikov
2015-03-13 23:37     ` Jan Vesely
2015-03-14 13:14       ` Emil Velikov
2015-02-27 18:07 ` [PATCH libdrm 8/8] Fix unused function warnings Jan Vesely
2015-03-18 18:37   ` [PATCH libdrm v2 " Jan Vesely
2015-03-18 18:37     ` [PATCH libdrm 9/8] Remove drmSetDebugMsgFunction and related infrastructure Jan Vesely
2015-03-20 21:06       ` Emil Velikov
2015-03-20 21:42         ` Jan Vesely [this message]
2015-03-20 17:33     ` [PATCH libdrm v2 8/8] Fix unused function warnings Emil Velikov
2015-02-27 22:27 ` [PATCH libdrm 0/8] Warnings fixes Emil Velikov
2015-03-13 23:20   ` Emil Velikov
2015-03-14  0:10     ` Jan Vesely

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=1426887747.3949.32.camel@rutgers.edu \
    --to=jan.vesely@rutgers.edu \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox