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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 10 Jul 2014 08:24:36 -0700
From:	<B_B_Singh@...L.com>
To:	<gregkh@...uxfoundation.org>
CC:	<tiwai@...e.de>, <Abhay_Salunke@...l.com>, <arnd@...db.de>,
	<kay@...y.org>, <ming.lei@...onical.com>, <sr@...x.de>,
	<teg@...m.no>, <Stuart_Hayes@...l.com>,
	<Srinivas_G_Gowda@...l.com>, <linux-kernel@...r.kernel.org>
Subject: RE: patch "firmware loader: allow disabling of udev as firmware
 loader" added to driver-core tree

Sorry Greg,

Here is the patch which I was referring to https://lkml.org/lkml/2014/6/4/327

I was doing the BIOS update test using the DELL BIOS-DUP's with the above patch.

Will provide you more technical analysis on why it is failing by tomorrow.

Regards
Balaji Singh

-----Original Message-----
From: Greg KH [mailto:gregkh@...uxfoundation.org]
Sent: Thursday, July 10, 2014 8:24 PM
To: Singh, B B
Cc: tiwai@...e.de; Abhay_Salunke@...l.com; arnd@...db.de; kay@...y.org; ming.lei@...onical.com; sr@...x.de; teg@...m.no; Hayes, Stuart; Gowda, Srinivas G; linux-kernel@...r.kernel.org
Subject: Re: patch "firmware loader: allow disabling of udev as firmware loader" added to driver-core tree

On Thu, Jul 10, 2014 at 08:10:01PM +0530, B_B_Singh@...L.com wrote:
> Resending the mail..
> 
> Hi All,
> 
> As I communicated earlier the test never passed with older BIOS DUPs.

That test? What patch? Please be explicit, I deal with thousands of patches and have no short term memory...

> Again today I have tested with 3.15.5 kernel with below patch applied, 
> & I don't see the BIOS getting updated. The BIOS update always failed 
> with below patch.
> 
> I'm not sure why the patch is getting committed even upon failure.

Because in that long and winding email thread I thought you said this patch _worked_. Obviously I was wrong, sorry, please suggest an alternative.

greg k-h
--
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