All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: Arunpravin <arunpravin.paneerselvam@amd.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Matthew Auld <matthew.auld@intel.com>,
	dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] drm/selftests: missing error code in igt_buddy_alloc_smoke()
Date: Mon, 7 Mar 2022 19:44:01 +0300	[thread overview]
Message-ID: <20220307164401.GE3315@kadam> (raw)
In-Reply-To: <091af126-751a-82fb-9a5c-9a7c4d614c4a@amd.com>

On Mon, Mar 07, 2022 at 05:14:59PM +0100, Christian König wrote:
> Pushed to drm-misc-next. Just one nit below.
> 
> Am 07.03.22 um 15:54 schrieb Arunpravin:
> > Reviewed-by:Arunpravin <Arunpravin.PaneerSelvam@amd.com>
> 
> Some people are picky about using the full name here.
> 

Signed-off-by is like signing a legal document to say that you have not
stolen anyone else's copyrighted works (SCO lawsuit).  So it should be
whatever name you use to sign legal documents.

regards,
dan carpenter


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: Arunpravin <arunpravin.paneerselvam@amd.com>,
	David Airlie <airlied@linux.ie>,
	kernel-janitors@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH] drm/selftests: missing error code in igt_buddy_alloc_smoke()
Date: Mon, 7 Mar 2022 19:44:01 +0300	[thread overview]
Message-ID: <20220307164401.GE3315@kadam> (raw)
In-Reply-To: <091af126-751a-82fb-9a5c-9a7c4d614c4a@amd.com>

On Mon, Mar 07, 2022 at 05:14:59PM +0100, Christian König wrote:
> Pushed to drm-misc-next. Just one nit below.
> 
> Am 07.03.22 um 15:54 schrieb Arunpravin:
> > Reviewed-by:Arunpravin <Arunpravin.PaneerSelvam@amd.com>
> 
> Some people are picky about using the full name here.
> 

Signed-off-by is like signing a legal document to say that you have not
stolen anyone else's copyrighted works (SCO lawsuit).  So it should be
whatever name you use to sign legal documents.

regards,
dan carpenter


  reply	other threads:[~2022-03-07 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 12:54 [PATCH] drm/selftests: missing error code in igt_buddy_alloc_smoke() Dan Carpenter
2022-03-07 12:54 ` Dan Carpenter
2022-03-07 14:54 ` Arunpravin
2022-03-07 14:54   ` Arunpravin
2022-03-07 16:14   ` Christian König
2022-03-07 16:14     ` Christian König
2022-03-07 16:44     ` Dan Carpenter [this message]
2022-03-07 16:44       ` Dan Carpenter

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=20220307164401.GE3315@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=airlied@linux.ie \
    --cc=arunpravin.paneerselvam@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=matthew.auld@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.