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: <20090730110938.GA16659@aftab>
Date:	Thu, 30 Jul 2009 13:09:39 +0200
From:	Borislav Petkov <borislav.petkov@....com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Borislav Petkov <petkovbb@...glemail.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Rusty Russell <rusty@...tcorp.com.au>,
	Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: linux-next: manual merge of the edac-amd tree with the rr tree

Hi Stephen,

On Thu, Jul 30, 2009 at 05:08:50PM +1000, Stephen Rothwell wrote:
> > thanks for fixing that. Yep, the topology patches in the edac tree are
> > not final yet, I've added them to the mix only because edac depends on
> > the node_id functionality. I'll fix them up later against the rr stuff.

I rediffed the topology bits against
cpumask:remove-topology_core_siblings-and-topology_thread_siblings-core.
patch from Rusty's tree so we should be good to go.

Also, I'm carrying couple of patches that should go through the x86 tree
and depending on when they go in, I'll drop them from mine. Just wanted
to give you heads up here in case you start getting merge conflicts :).

Thanks.

-- 
Regards/Gruss,
Boris.

Operating | Advanced Micro Devices GmbH
  System  | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
 Research | Geschäftsführer: Thomas M. McCoy, Giuliano Meroni
  Center  | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
  (OSRC)  | Registergericht München, 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