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]
Message-ID: <20110412111300.GE20607@amd.com>
Date:	Tue, 12 Apr 2011 13:13:00 +0200
From:	"Roedel, Joerg" <Joerg.Roedel@....com>
To:	Sergei Shtylyov <sshtylyov@...sta.com>
CC:	Alan Stern <stern@...land.harvard.edu>,
	Borislav Petkov <bp@...en8.de>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	"Xu, Andiry" <Andiry.Xu@....com>,
	USB list <linux-usb@...r.kernel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6] USB host: Fix lockdep warning in AMD PLL quirk

On Tue, Apr 12, 2011 at 06:59:27AM -0400, Sergei Shtylyov wrote:
> Hello.
> 
> On 12-04-2011 10:41, Roedel, Joerg wrote:
> 
> >>> Hmm, I see how it can be done differently, but no real bug.
> 
> >> Never mind, you're right.  In the no-race case, the initial count is
> >> always going to be 0, and so incrementing info.probe_count is the right
> >> thing to do.
> 
> > Okay, cool. So now that we have settled on this I removed the last
> > occurence of '2.6.38' from the changelog and here is the result. No
> > code changes since v5.
> 
>     I've pointed out the mistake in the code that you didn't fix... :-(

Argh, sorry, I missed this comment from you. I'll fix this.

	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632

--
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