From: Michele CURTI <michele.curti@gmail.com>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "Koenig, Christian" <Christian.Koenig@amd.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: [PATCH v2 0/2] drm/radeon: use NULL instead of zero
Date: Mon, 5 May 2014 22:26:31 +0200 [thread overview]
Message-ID: <20140505202631.GA404@ativ> (raw)
In-Reply-To: <A3397C8B8B789E45844E7EC5DEAD89D040EEF93D@satlexdag05.amd.com>
This patches replace 0 with NULL when NULL pointers in radeon driver.
The first in object functions.
the second in clearstate headers.
Changes from v1:
- splitted in two separated patches
On Mon, May 05, 2014 at 12:53:58PM +0000, Deucher, Alexander wrote:
> > -----Original Message-----
> > From: Michele CURTI [mailto:michele.curti@gmail.com]
> > Sent: Saturday, May 03, 2014 9:55 AM
> > To: Deucher, Alexander; Koenig, Christian; airlied@linux.ie
> > Cc: linux-next@vger.kernel.org
> > Subject: [PATCH] drm/radeon: use NULL instead of zero
> >
> >
> > Use NULL instead of zero for NULL pointers
> >
> > Signed-off-by: Michele Curti <michele.curti@gmail.com>
>
> Can you break this into two patches? One that changes that clearstate headers and one that changes object functions?
>
> Thanks,
>
> Alex
>
Sure!
Or at least, I'm going to try..
Michele
next prev parent reply other threads:[~2014-05-05 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 13:55 [PATCH] drm/radeon: use NULL instead of zero Michele CURTI
2014-05-05 12:53 ` Deucher, Alexander
2014-05-05 20:26 ` Michele CURTI [this message]
2014-05-06 16:28 ` [PATCH v2 0/2] " Deucher, Alexander
2014-05-05 20:29 ` [PATCH v2 1/2] drm/radeon: use NULL instead of zero in object functions Michele CURTI
2014-05-05 20:32 ` [PATCH v2 2/2] drm/radeon: use NULL instead of zero in clearstate headers Michele CURTI
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=20140505202631.GA404@ativ \
--to=michele.curti@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=airlied@linux.ie \
--cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).