From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82681] gpu/drm/radeon/cik.c:1849: bad nested conditions ?
Date: Thu, 21 Aug 2014 16:55:03 +0000 [thread overview]
Message-ID: <bug-82681-2300-1HAGcoJkN2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82681-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82681
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #2 from Alex Deucher <alexdeucher@gmail.com> ---
Earlier versions of the code had the core part of the loop split out into a
separate function so it needed the additional checks in case it was called from
elsewhere. I left them in as a reminder in case the code is ever restructured.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-21 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-82681-2300@https.bugzilla.kernel.org/>
2014-08-21 15:31 ` [Bug 82681] gpu/drm/radeon/cik.c:1849: bad nested conditions ? bugzilla-daemon
2014-08-21 16:55 ` bugzilla-daemon [this message]
2014-08-21 17:03 ` 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-82681-2300-1HAGcoJkN2@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 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.