All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
	Nirmoy Das <nirmoy.das@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Matthew Auld <matthew.auld@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RFC PATCH 1/2] drm/i915: Add a function to mmap framebuffer obj
Date: Mon, 20 Mar 2023 11:04:45 +0100	[thread overview]
Message-ID: <7c855cce-be3d-c50f-a093-3ebccca17854@linux.intel.com> (raw)
In-Reply-To: <ZBeq/bqrpeuUMkp0@ashyti-mobl2.lan>


On 3/20/2023 1:38 AM, Andi Shyti wrote:
> Hi Nirmoy,
>
> On Thu, Mar 16, 2023 at 06:22:19PM +0100, Nirmoy Das wrote:
>> Implement i915_gem_fb_mmap() to enable fb_ops.fb_mmap()
>> callback for i915's framebuffer objects.
>>
>> v2: add a comment why i915_gem_object_get() needed(Andi).
>>
>> Cc: Matthew Auld <matthew.auld@intel.com>
>> Cc: Andi Shyti <andi.shyti@linux.intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> I think you can fire the PATCH here instead of the RFC. Looks
> good to me.
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>


Thanks, I will do that.

Nirmoy

>
> Andi

WARNING: multiple messages have this Message-ID (diff)
From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
	Nirmoy Das <nirmoy.das@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Matthew Auld <matthew.auld@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH 1/2] drm/i915: Add a function to mmap framebuffer obj
Date: Mon, 20 Mar 2023 11:04:45 +0100	[thread overview]
Message-ID: <7c855cce-be3d-c50f-a093-3ebccca17854@linux.intel.com> (raw)
In-Reply-To: <ZBeq/bqrpeuUMkp0@ashyti-mobl2.lan>


On 3/20/2023 1:38 AM, Andi Shyti wrote:
> Hi Nirmoy,
>
> On Thu, Mar 16, 2023 at 06:22:19PM +0100, Nirmoy Das wrote:
>> Implement i915_gem_fb_mmap() to enable fb_ops.fb_mmap()
>> callback for i915's framebuffer objects.
>>
>> v2: add a comment why i915_gem_object_get() needed(Andi).
>>
>> Cc: Matthew Auld <matthew.auld@intel.com>
>> Cc: Andi Shyti <andi.shyti@linux.intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> I think you can fire the PATCH here instead of the RFC. Looks
> good to me.
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>


Thanks, I will do that.

Nirmoy

>
> Andi

  reply	other threads:[~2023-03-20 10:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 17:22 [Intel-gfx] [RFC PATCH 1/2] drm/i915: Add a function to mmap framebuffer obj Nirmoy Das
2023-03-16 17:22 ` Nirmoy Das
2023-03-16 17:22 ` [Intel-gfx] [RFC PATCH 2/2] drm/i915/display: Implement fb_mmap callback function Nirmoy Das
2023-03-16 17:22   ` Nirmoy Das
2023-03-17  9:39   ` [Intel-gfx] " Jani Nikula
2023-03-17  9:39     ` Jani Nikula
2023-03-17 10:08     ` [Intel-gfx] " Das, Nirmoy
2023-03-17 10:08       ` Das, Nirmoy
2023-03-20  0:40   ` [Intel-gfx] " Andi Shyti
2023-03-20  0:40     ` Andi Shyti
2023-03-20  0:38 ` [Intel-gfx] [RFC PATCH 1/2] drm/i915: Add a function to mmap framebuffer obj Andi Shyti
2023-03-20  0:38   ` Andi Shyti
2023-03-20 10:04   ` Das, Nirmoy [this message]
2023-03-20 10:04     ` Das, Nirmoy
  -- strict thread matches above, loose matches on Subject: below --
2023-03-07 14:46 [Intel-gfx] " Nirmoy Das
2023-03-13 18:37 ` Andi Shyti
2023-03-14  9:18   ` Das, Nirmoy

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=7c855cce-be3d-c50f-a093-3ebccca17854@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=matthew.auld@intel.com \
    --cc=nirmoy.das@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.