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:	Thu, 14 Nov 2013 15:21:25 +0100
From:	Johannes Thumshirn <johannes.thumshirn@....de>
To:	Borislav Petkov <bp@...en8.de>
CC:	Mauro Carvalho Chehab <m.chehab@...sung.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Borislav Petkov <bp@...e.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Doug Thompson <dougthompson@...ssion.com>,
	Johannes Thumshirn <johannes.thumshirn@....de>,
	Robert Richter <rric@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	<linux-edac@...r.kernel.org>,
	Aristeu Rozanski Filho <arozansk@...hat.com>
Subject: Re: [GIT PULL] mpc85xx_edac changes for 3.13

On Thu, Nov 14, 2013 at 12:24:18PM +0100, Borislav Petkov wrote:
> On Thu, Nov 14, 2013 at 09:18:43AM -0200, Mauro Carvalho Chehab wrote:
> > So, in practice, Borislav was working as a maintainer for amd64 EDAC
> > patches, and I working mainly as Intel EDAC maintainer. The (few)
> > other arm EDAC patches were either coming via my tree or via Boris
> > tree, depending on who got them first.
>
> Yeah, and I think this has worked pretty good in the past so if you want
> to, we can continue the same thing of sharing the load on EDAC patches
> and we both do interim maintainers until Doug steps in.
>
> And since it won't change any workflow for Linus, he's probably fine
> with it too.
>
> Yes, no? Comments?

OK for me. For the MPC85xx EDAC I'll do the testing then and either Borislav or
Mauro send them upstream.

Regards,
	Johannes
--
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