lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 18 Mar 2015 06:53:20 -0700
From:	"H.J. Lu" <hjl.tools@...il.com>
To:	Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
Cc:	Jiri Olsa <jolsa@...hat.com>,
	Adrian Hunter <adrian.hunter@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Namhyung Kim <namhyung@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, Jiri Olsa <jolsa@...nel.org>
Subject: Re: [PATCH] Check ARCH and IS_64_BIT instead of IS_X86_64 in perf

On Wed, Mar 18, 2015 at 6:10 AM, Arnaldo Carvalho de Melo
<arnaldo.melo@...il.com> wrote:
> Em Wed, Mar 18, 2015 at 10:43:44AM +0100, Jiri Olsa escreveu:
>> On Wed, Mar 18, 2015 at 10:24:10AM +0200, Adrian Hunter wrote:
>> > Hi
>> >
>> > +Arnaldo
>> > +Jiri
>> >
>> > I would change the commit message and subject. Say:
>> >
>> > Subject: perf tools: Fix perf-read-vdsox32 not building and lib64 install dir
>> >
>> > Commit:
>> >
>> >   c6e5e9fbc3ea ("perf tools: Fix building error in x86_64 when dwarf unwind is on")
>> >
>> > removed the definition of IS_X86_64 but not all places
>> > using it, with the consequence that perf-read-vdsox32
>> > would not be built anymore, and the default lib install
>> > directory was 'lib' instead of 'lib64'.
>> >
>> > Also needs to go to v3.19.
>> >
>> > Otherwise:
>> >
>> > Acked-by: Adrian Hunter <adrian.hunter@...el.com>
>> > Cc: stable@...r.kernel.org # 3.19
>>
>> Acked-by: Jiri Olsa <jolsa@...nel.org>
>
> Changed the commit log and applied, thanks,

Thanks.


-- 
H.J.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ