From: kbuild test robot <lkp@intel.com>
To: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
Subject: Re: [PATCH 2/3] perf/x86/amd/uncore: Dynamically allocate uncore counters
Date: Thu, 12 Jan 2017 21:12:58 +0800 [thread overview]
Message-ID: <201701122147.So3CUDMg%fengguang.wu@intel.com> (raw)
In-Reply-To: <11f5b2f7a63c0123cd2f9ba9cb4693c6feca1205.1484148262.git.Janakarajan.Natarajan@amd.com>
Hi Janakarajan,
[auto build test WARNING on next-20170111]
[also build test WARNING on v4.10-rc3]
[cannot apply to tip/x86/core v4.9-rc8 v4.9-rc7 v4.9-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Janakarajan-Natarajan/perf-x86-amd-uncore-Update-AMD-uncore-driver/20170112-184113
coccinelle warnings: (new ones prefixed by >>)
>> arch/x86/events/amd/uncore.c:365:2-7: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to avoid passing NULL values.
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2017-01-12 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 16:02 [PATCH 0/3] perf/x86/amd/uncore: Update AMD uncore driver Janakarajan Natarajan
2017-01-11 16:02 ` [PATCH 1/3] perf/x86/amd/uncore: Update AMD uncore to rename L2 to LLC Janakarajan Natarajan
2017-01-11 16:02 ` [PATCH 2/3] perf/x86/amd/uncore: Dynamically allocate uncore counters Janakarajan Natarajan
2017-01-12 9:20 ` Peter Zijlstra
2017-01-13 0:48 ` Natarajan, Janakarajan
2017-01-13 8:58 ` Peter Zijlstra
2017-01-12 13:12 ` [PATCH] perf/x86/amd/uncore: fix ifnullfree.cocci warnings kbuild test robot
2017-01-12 13:12 ` kbuild test robot [this message]
2017-01-11 16:02 ` [PATCH 3/3] perf/x86/amd/uncore: Update sysfs attributes for Family17h processors Janakarajan Natarajan
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=201701122147.So3CUDMg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Janakarajan.Natarajan@amd.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=suravee.suthikulpanit@amd.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
Powered by JetHome