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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 18 Apr 2012 15:59:49 +0000
From:	"Heasley, Seth" <seth.heasley@...el.com>
To:	Samuel Ortiz <sameo@...ux.intel.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Ralston, James D" <james.d.ralston@...el.com>
Subject: RE: [PATCH 3/3] lpc_sch: Add Intel Centerton Multifunction Device
 support

Hi Samuel,

>Is the pci_ids.h change already in ? If not, I should take it at the
>same time so that we don't break compilation.

It was submitted just prior to my sending this patch.

>> @@ -68,7 +69,7 @@ static struct resource wdt_sch_resource = {
>>
>>  static struct mfd_cell tunnelcreek_cells[] = {
>>  	{
>> -		.name = "tunnelcreek_wdt",
>> +		.name = "ie6xx_wdt",
>>  		.num_resources = 1,
>>  		.resources = &wdt_sch_resource,
>>  	},
>This one should be part of your upcoming watchdog driver patch (as a
>separate patch that I'd take).

I'm actually not submitting a watchdog patch.  The maintainer already has code for this driver and is converting it to the new watchdog API.  In discussions with him, we agreed to the renaming of the driver, which was submitted for a previous platform.  He'll be committing the new code in the next couple of weeks, so I made this change in anticipation of the driver making it upstream.  I can certainly submit this separately, but my thinking was that it's all connected to Centerton enabling since it uses the same driver.  Let me know what you'd like me to do.

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