dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Maninder Singh <maninder1.s@samsung.com>,
	airlied@linux.ie, alexander.deucher@amd.com,
	michel.daenzer@amd.com, monk.liu@amd.com,
	maarten.lankhorst@canonical.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, pankaj.m@samsung.com
Subject: Re: [PATCH 1/1] gpu/drm: use kzalloc for allocating one thing
Date: Fri, 26 Jun 2015 09:40:44 +0200	[thread overview]
Message-ID: <558D01FC.7090606@amd.com> (raw)
In-Reply-To: <20150626073719.GV25769@phenom.ffwll.local>

On 26.06.2015 09:37, Daniel Vetter wrote:
> On Fri, Jun 26, 2015 at 09:34:43AM +0200, Daniel Vetter wrote:
>> On Fri, Jun 26, 2015 at 11:54:10AM +0530, Maninder Singh wrote:
>>> Use kzalloc rather than kcalloc(1.. for allocating
>>> one thing.
>>>
>>> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
>>> Reviewed-by: Vaneet Narang <v.narang@samsung.com>
>> Applied to drm-misc, thanks.
> And dropped again since I didn't realize this is for amdgpu and not core
> drm.

I was just about to complain on the confusing patch subject :)

So please fix the subject lines of both your patches to something like 
"drm/amdgpu:" and send them out again.

With that fixed both patches are Reviewed-by: Christian König 
<christian.koenig@amd.com>

Regards,
Christian.

> -Daniel

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

      reply	other threads:[~2015-06-26  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  6:24 [PATCH 1/1] gpu/drm: use kzalloc for allocating one thing Maninder Singh
2015-06-26  7:34 ` Daniel Vetter
2015-06-26  7:37   ` Daniel Vetter
2015-06-26  7:40     ` Christian König [this message]

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=558D01FC.7090606@amd.com \
    --to=christian.koenig@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@canonical.com \
    --cc=maninder1.s@samsung.com \
    --cc=michel.daenzer@amd.com \
    --cc=monk.liu@amd.com \
    --cc=pankaj.m@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox