All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm: Move drm_format_num_planes() to drm_crtc.c
Date: Fri, 20 Apr 2012 13:29:11 +0100	[thread overview]
Message-ID: <CAPM=9ty7GvQHYHoZ-Efh2U2L183mTUBGUw-F5BBFguqdshwwDg@mail.gmail.com> (raw)
In-Reply-To: <20120420122341.GA13065@intel.com>

On Fri, Apr 20, 2012 at 1:23 PM, Ville Syrjälä
<ville.syrjala@linux.intel.com> wrote:
> On Fri, Apr 20, 2012 at 12:43:03PM +0100, Dave Airlie wrote:
>> On Thu, Apr 5, 2012 at 7:35 PM,  <ville.syrjala@linux.intel.com> wrote:
>> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> >
>> > There will be a need for this function in drm_crtc.c later. This
>> > avoids making drm_crtc.c depend on drm_crtc_helper.c.
>>
>> Hi Ville,
>>
>> I've applied these 4 patches, but I might have lost some others for
>> you, let me know if there is some other stuff I should be reviewing
>> for -next.
>
> IIRC only one patch fell through the cracks:
> Subject: [PATCH] drm: Unify and fix idr error handling
> Message-Id: <1331834311-30757-1-git-send-email-ville.syrjala@linux.intel.com>

Thanks I'll take a look at that,

>
> BTW you never gave any statement wrt. removing NV12M and YUV420M from
> drm_fourcc.h. I can send a patch if you agree, and if not, well then
> someone has to actually change the code to treat them exactly the same
> as NV12 and YUV420.

I'm probably not qualified, if you and jbarnes and say one other
non-Intel person agree, then send the patch with R-b and I'll apply
it.

Dave.

  reply	other threads:[~2012-04-20 12:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 18:35 [PATCH 1/4] drm: Move drm_format_num_planes() to drm_crtc.c ville.syrjala
2012-04-05 18:35 ` [PATCH 2/4] drm: Add drm_format_plane_cpp() utility function ville.syrjala
2012-04-05 18:35 ` [PATCH 3/4] drm: Add drm_format_{horz, vert}_chroma_subsampling() utility functions ville.syrjala
2012-04-11 18:53   ` Roland Scheidegger
2012-04-12 12:23     ` Ville Syrjälä
2012-04-13  2:42       ` Roland Scheidegger
2012-04-13 12:09         ` Ville Syrjälä
2012-04-05 18:35 ` [PATCH 4/4] drm: Add sanity checks to framebuffer creation ville.syrjala
2012-04-20 11:43 ` [PATCH 1/4] drm: Move drm_format_num_planes() to drm_crtc.c Dave Airlie
2012-04-20 12:23   ` Ville Syrjälä
2012-04-20 12:29     ` Dave Airlie [this message]
2012-04-20 12:48       ` Rob Clark
2012-04-20 13:49         ` Ville Syrjälä
2012-04-20 14:22           ` Rob Clark
2012-04-21  4:00             ` InKi Dae

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='CAPM=9ty7GvQHYHoZ-Efh2U2L183mTUBGUw-F5BBFguqdshwwDg@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.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 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.