linux-kernel - RE: [PATCH 0/3] AMD thresholding fixes

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: <3908561D78D1C84285E8C5FCA982C28F170F3C53@ORSMSX104.amr.corp.intel.com>
Date:	Wed, 25 Apr 2012 16:49:52 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Borislav Petkov <bp@...64.org>,
	EDAC devel <linux-edac@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
CC:	Borislav Petkov <borislav.petkov@....com>
Subject: RE: [PATCH 0/3] AMD thresholding fixes

> If there are no issues, I'll add the queue to linux-next (I don't see a
> branch from ras.git in linux-next, btw, which is strange).

Patches so far have been flowing from "ras" to "tip" to "linus". It
hasn't quite been clear how linux-next fits into this. If we export
to -next, then are we planning on sending those directly to linus,
bypassing tip?

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