All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepak Singh Rawat <drawat@vmware.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: Expose "FB_DAMAGE_CLIPS" property to atomic aware user-space only
Date: Tue, 16 Apr 2019 22:34:54 +0000	[thread overview]
Message-ID: <a11ecbfae515cfd1ebb7071a72b341fa26ce3818.camel@vmware.com> (raw)
In-Reply-To: <CAKMK7uFrbyWNBazsdfF2_qQZ73f6i9EKAdzPwDnVVx7+bK3S6A@mail.gmail.com>


> > 
> > If you mean ssh on annarchy.freedesktop.org, I already have one
> > with
> > username - drawat
> 
> You're added. Please check out the dim toturial and pls ask any
> questions here or on irc or wherever - drm(-misc) maintainers are
> happy to help out.
> -Daniel
> 

Hi I followed the instruction at 
https://drm.pages.freedesktop.org/maintainer-tools/getting-started.html
 and submitted my patch, I see that drm-tip has a lot of commits with
myself as author(https://cgit.freedesktop.org/drm/drm-tip/log/). Is
this expected? Or did I messed up something.

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-04-16 22:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 17:28 [PATCH] drm: Expose "FB_DAMAGE_CLIPS" property to atomic aware user-space only Deepak Singh Rawat
2019-04-16  7:42 ` Daniel Vetter
2019-04-16 16:21   ` Deepak Singh Rawat
2019-04-16 18:15     ` Daniel Vetter
2019-04-16 18:28       ` Deepak Singh Rawat
2019-04-16 19:27         ` Daniel Vetter
2019-04-16 22:34           ` Deepak Singh Rawat [this message]
2019-04-17  7:07             ` Daniel Vetter

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=a11ecbfae515cfd1ebb7071a72b341fa26ce3818.camel@vmware.com \
    --to=drawat@vmware.com \
    --cc=Linux-graphics-maintainer@vmware.com \
    --cc=daniel@ffwll.ch \
    --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.