linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH 09/13] drm/irq: Make pipe unsigned and name consistent
       [not found]   ` <20150812153214.GL17734@phenom.ffwll.local>
@ 2015-10-30 18:38     ` Ilia Mirkin
  0 siblings, 0 replies; only message in thread
From: Ilia Mirkin @ 2015-10-30 18:38 UTC (permalink / raw)
  To: Daniel Vetter; +Cc: Thierry Reding, Daniel Vetter, dri-devel, linux-kernel

On Wed, Aug 12, 2015 at 11:32 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Aug 12, 2015 at 05:00:31PM +0200, Thierry Reding wrote:
>> From: Thierry Reding <treding@nvidia.com>
>>
>> Name all references to the pipe number (CRTC index) consistently to make
>> it easier to distinguish which is a pipe number and which is a pointer
>> to struct drm_crtc.
>>
>> While at it also make all references to the pipe number unsigned because
>> there is no longer any reason why it should ever be negative.
>>
>> Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> There's 2 "int crtc" and one "int pipe" (without the unsigned) left after
> this patch. Can you please do a follow-up? Applied this meanwhile.

4.3 is about to get released, and the regression for nouveau that this
change introduces (https://bugzilla.kernel.org/show_bug.cgi?id=106431)
is still not fixed.

Can you remove the warn for now or explicitly allow ~0U? Don't want to
start spewing warns for everyone with a pre-tesla nvidia gpu...

Thanks,

  -ilia

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-10-30 18:38 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1439391635-29166-1-git-send-email-thierry.reding@gmail.com>
     [not found] ` <1439391635-29166-9-git-send-email-thierry.reding@gmail.com>
     [not found]   ` <20150812153214.GL17734@phenom.ffwll.local>
2015-10-30 18:38     ` [PATCH 09/13] drm/irq: Make pipe unsigned and name consistent Ilia Mirkin

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).