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, 5 Feb 2014 15:34:42 -0500 (EST)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
cc:	Namhyung Kim <namhyung@...nel.org>, linux-kernel@...r.kernel.org,
	Chad Paradis <chad.paradis@...t.maine.edu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [patch] perf tools: perf list broken on ARM

On Thu, 9 Jan 2014, Arnaldo Carvalho de Melo wrote:

> Em Thu, Jan 09, 2014 at 09:37:03PM +0900, Namhyung Kim escreveu:
> > 2014-01-09 (목), 09:12 -0300, Arnaldo Carvalho de Melo:
> > > Em Thu, Jan 09, 2014 at 05:17:27PM +0900, Namhyung Kim escreveu:
> > > > Hi Vince,
> > > > 
> > > > On Wed, 8 Jan 2014 16:30:17 -0500 (EST), Vince Weaver wrote:
> > > > > just checking on the status of this patch.  Am I sending it to the wrong 
> > > > > place?  Did it get lost in the post-holiday e-mail purges?  
> > > > >
> > > > > The bug is annoying if you're trying to use perf on ARM systems.
> > > > 
> > > > Right, acme, would you please merge this?
> > > 
> > > I will, but having a patch authored by someone and Acked-by that same
> > > person looks weird, so, to clarify, this was written by Vince, acked by
> > > you, right?
> > 
> > You seemed to be confused - it's not authored by me.  He was just
> > referring a problematic commit b41f1cec91c3 which was written by me.  So
> > yeah, this commit was written by Vince.
> 
> You are right, I saw that Author: line in the changeset comment, close
> to the start of the message and got confused, thanks for clarifying.

Do I need to re-send this patch?  It still applies cleanly to 3.14-rc1.

Vince

Powered by blists - more mailing lists