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: <CALCETrVrOxQc1_qaYsa-rPMNYs4vdiFBgULqp2K7VTL1j=Qhvg@mail.gmail.com>
Date:	Sun, 31 Jan 2016 14:46:35 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	Corey Minyard <minyard@....org>
Cc:	OpenIPMI Developers <openipmi-developer@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jean Delvare <jdelvare@...e.de>,
	Andy Lutomirski <luto@...nel.org>,
	Corey Minyard <cminyard@...sta.com>
Subject: Re: [PATCH 2/4] dmi: Add a DMI firmware node and handling

On Fri, Jan 29, 2016 at 2:43 PM,  <minyard@....org> wrote:
> From: Corey Minyard <cminyard@...sta.com>
>
> This is so that an IPMI platform device can be created from a
> DMI firmware entry.

This doesn't apply for me.  What's it based on?

--Andy

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ