dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202735] CONFIG_DRM_TTM does not have name in Kconfig, so it is invisble for menuconfig
Date: Mon, 04 Mar 2019 12:57:46 +0000	[thread overview]
Message-ID: <bug-202735-2300-TZiOJ2y3UF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202735-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202735

--- Comment #3 from Jani Nikula (jani.nikula@intel.com) ---
Arguably not a bug in kernel.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-03-04 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 23:15 [Bug 202735] New: CONFIG_DRM_TTM does not have name in Kconfig, so it is invisble for menuconfig bugzilla-daemon
2019-03-04  9:36 ` [Bug 202735] " bugzilla-daemon
2019-03-04  9:53 ` bugzilla-daemon
2019-03-04 12:57 ` bugzilla-daemon [this message]
2019-03-04 13:42 ` bugzilla-daemon

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-202735-2300-TZiOJ2y3UF@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).