dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36522] Caught 16-bit read from uninitialized memory in drm_fb_helper_setcmap
Date: Thu, 17 Feb 2022 18:19:38 +0000	[thread overview]
Message-ID: <bug-36522-2300-oyuX6gmQ4f@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-36522-2300@https.bugzilla.kernel.org/>

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

Christian Casteyde (casteyde.christian@free.fr) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |OBSOLETE

--- Comment #19 from Christian Casteyde (casteyde.christian@free.fr) ---
Closing as too old and I do not have the hardware anymore to reproduce.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-02-17 18:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36522-2300@https.bugzilla.kernel.org/>
2012-05-14 14:25 ` [Bug 36522] Caught 16-bit read from uninitialized memory in drm_fb_helper_setcmap bugzilla-daemon
2012-08-05 21:28 ` bugzilla-daemon
2012-10-21 21:49 ` bugzilla-daemon
2013-01-03 12:55 ` bugzilla-daemon
2013-08-31 17:11 ` bugzilla-daemon
2013-12-23 13:40 ` bugzilla-daemon
2016-07-10 11:23 ` bugzilla-daemon
2016-08-04 15:03 ` bugzilla-daemon
2016-08-04 15:04 ` bugzilla-daemon
2016-08-05  7:54 ` bugzilla-daemon
2016-08-06  2:33 ` bugzilla-daemon
2016-08-06  5:58 ` bugzilla-daemon
2022-02-17 18:19 ` bugzilla-daemon [this message]
2022-02-17 18:19 ` 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-36522-2300-oyuX6gmQ4f@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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).