Re: [PATCH 4.1 099/123] perf hists browser: Take the --comm, --dsos, etc filters into account
From: Luis Henriques
Date: Tue Aug 11 2015 - 04:53:09 EST
On Sun, Aug 09, 2015 at 08:12:41PM +0200, Andre Tomt (LKML) wrote:
> On 09. aug. 2015 00:09, Greg Kroah-Hartman wrote:
> >4.1-stable review patch. If anyone has any objections, please let me know.
> >
> >------------------
> >
> >From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
> >
> >commit 9c0fa8dd3d58de8b688fda758eea1719949c7f0a upstream.
>
> This commit needs upstream commit 0bc2f2f7d080561cc484d2d0a162a9396bed3383
> as well to fix the following build error
>
Thanks, I'm queuing this commit for the 3.16 kernel as well. Also
CC'ing Kamal as it looks like 3.19 needs it too.
Cheers,
--
Luís
>
> CC ui/browsers/hists.o
> ui/browsers/hists.c: In function 'hist_browser__has_filter':
> ui/browsers/hists.c:48:68: error: 'struct symbol_conf' has no member named
> 'has_filter'
> return hists__has_filter(hb->hists) || hb->min_pcnt ||
> symbol_conf.has_filter;
> ^
> ui/browsers/hists.c:49:1: error: control reaches end of non-void function
> [-Werror=return-type]
> }
> ^
> cc1: all warnings being treated as errors
> /disks/build/data/linux-4.1.5-rc1/tools/build/Makefile.build:68: recipe for
> target 'ui/browsers/hists.o' failed
> make[4]: *** [ui/browsers/hists.o] Error 1
> /disks/build/data/linux-4.1.5-rc1/tools/build/Makefile.build:107: recipe for
> target 'browsers' failed
> make[3]: *** [browsers] Error 2
> /disks/build/data/linux-4.1.5-rc1/tools/build/Makefile.build:107: recipe for
> target 'ui' failed
> make[2]: *** [ui] Error 2
> Makefile.perf:366: recipe for target 'libperf-in.o' failed
> make[1]: *** [libperf-in.o] Error 2
> Makefile:68: recipe for target 'all' failed
> make: *** [all] Error 2
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/