All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: kbuild-all@01.org, dri-devel@lists.freedesktop.org
Subject: [radeon-alex:drm-next-3.12-wip 31/90] WARNING: kfree(NULL) is safe this check is probably not required
Date: Fri, 23 Aug 2013 07:43:11 +0800	[thread overview]
Message-ID: <20130822234311.GB14463@localhost> (raw)
In-Reply-To: <52163013.TL5RMI4ybbr4q9xC%fengguang.wu@intel.com>


Hi Alex,

FYI, there are new warnings show up in

tree:   git://people.freedesktop.org/~agd5f/linux.git drm-next-3.12-wip
head:   21419df38d4ba010b1ea80e2f91b853c8c3de7e5
commit: 38306848032ac045ac5a5f3145271bc01176883e [31/90] drm/radeon/dpm: add support for parsing the atom powertune table

scripts/checkpatch.pl 0001-drm-radeon-dpm-add-support-for-parsing-the-atom-powe.patch

WARNING: kfree(NULL) is safe this check is probably not required
#73: drivers/gpu/drm/radeon/r600_dpm.c:1079:
+	if (rdev->pm.dpm.dyn_state.cac_tdp_table)
+		kfree(rdev->pm.dpm.dyn_state.cac_tdp_table);

The warning also shows up in many of the follow up patches.

[radeon-alex:drm-next-3.12-wip 32/90] WARNING: kfree(NULL) is safe
[radeon-alex:drm-next-3.12-wip 35/90] WARNING: kfree(NULL) is safe
[radeon-alex:drm-next-3.12-wip 36/90] WARNING: kfree(NULL) is safe
[radeon-alex:drm-next-3.12-wip 38/90] WARNING: kfree(NULL) is safe
[radeon-alex:drm-next-3.12-wip 39/90] WARNING: kfree(NULL) is safe

---
0-DAY kernel build testing backend              Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

           reply	other threads:[~2013-08-22 23:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <52163013.TL5RMI4ybbr4q9xC%fengguang.wu@intel.com>]

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=20130822234311.GB14463@localhost \
    --to=fengguang.wu@intel.com \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@01.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.