From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754157AbbEOGnM (ORCPT ); Fri, 15 May 2015 02:43:12 -0400 Received: from terminus.zytor.com ([198.137.202.10]:58124 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753869AbbEOGnK (ORCPT ); Fri, 15 May 2015 02:43:10 -0400 Date: Thu, 14 May 2015 23:42:43 -0700 From: tip-bot for Arnaldo Carvalho de Melo Message-ID: Cc: namhyung@kernel.org, eranian@google.com, acme@redhat.com, mingo@kernel.org, dsahern@gmail.com, adrian.hunter@intel.com, tglx@linutronix.de, bp@suse.de, hpa@zytor.com, jolsa@redhat.com, linux-kernel@vger.kernel.org, fweisbec@gmail.com, dzickus@redhat.com Reply-To: acme@redhat.com, eranian@google.com, namhyung@kernel.org, dsahern@gmail.com, mingo@kernel.org, tglx@linutronix.de, bp@suse.de, adrian.hunter@intel.com, dzickus@redhat.com, fweisbec@gmail.com, jolsa@redhat.com, linux-kernel@vger.kernel.org, hpa@zytor.com To: linux-tip-commits@vger.kernel.org Subject: [tip:perf/core] perf kmem: Fix compiler warning about may be accessing uninitialized variable Git-Commit-ID: 08a9b9857fc2d77600f09f3d342f6c64d25083b2 X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: 08a9b9857fc2d77600f09f3d342f6c64d25083b2 Gitweb: http://git.kernel.org/tip/08a9b9857fc2d77600f09f3d342f6c64d25083b2 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 11 May 2015 11:41:17 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 12 May 2015 09:59:47 -0300 perf kmem: Fix compiler warning about may be accessing uninitialized variable The last argument to strtok_r doesn't need to be initialized, its just a placeholder to make this routine reentrant, but gcc doesn't know about that and complains, breaking the build, fix it by setting it to NULL. Fixes: 0e11115644b3 ("perf kmem: Print gfp flags in human readable string") Cc: Adrian Hunter Cc: Borislav Petkov Cc: David Ahern Cc: Don Zickus Cc: Frederic Weisbecker Cc: Jiri Olsa Cc: Namhyung Kim Cc: Stephane Eranian Link: http://lkml.kernel.org/n/tip-iyyvkbnkrd9g19f6ta9zfkem@git.kernel.org Signed-off-by: Arnaldo Carvalho de Melo --- tools/perf/builtin-kmem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/builtin-kmem.c b/tools/perf/builtin-kmem.c index e0173c7..254614b 100644 --- a/tools/perf/builtin-kmem.c +++ b/tools/perf/builtin-kmem.c @@ -713,7 +713,7 @@ static int parse_gfp_flags(struct perf_evsel *evsel, struct perf_sample *sample, .size = sample->raw_size, }; struct trace_seq seq; - char *str, *pos; + char *str, *pos = NULL; if (nr_gfps) { struct gfp_flag key = {