linux-kernel - Re: [PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd driver.

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:	Tue, 5 Jul 2011 09:15:58 -0700
From:	Greg KH <greg@...ah.com>
To:	Subhasish Ghosh <subhasish@...tralsolutions.com>
Cc:	"open list:STAGING SUBSYSTEM" <devel@...verdev.osuosl.org>,
	sachi@...tralsolutions.com,
	davinci-linux-open-source@...ux.davincidsp.com,
	stalin.s@...tralsolutions.com, Greg Kroah-Hartman <gregkh@...e.de>,
	open list <linux-kernel@...r.kernel.org>, m-watkins@...com,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd
 driver.

On Tue, Jun 28, 2011 at 02:01:12PM -0700, Greg KH wrote:
> On Tue, May 31, 2011 at 01:15:39PM +0530, Subhasish Ghosh wrote:
> > This patch adds the pruss MFD driver and associated include files.
> > For details regarding the PRUSS please refer the folowing link:
> > http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit_Subsystem
> > 
> > The rational behind the MFD driver being the fact that multiple devices can
> > be implemented on the cores independently. This is determined by the nature
> > of the program which is loaded into the PRU's instruction memory.
> > A device may be de-initialized and another loaded or two different devices
> > can be run simultaneously on the two cores.
> > It's also possible, as in our case, to implement a single device on both
> > the PRU's resulting in improved load sharing.
> > 
> > Signed-off-by: Subhasish Ghosh <subhasish@...tralsolutions.com>
> 
> Please refresh my memory as to why this can't get merged into the
> "normal" part of the kernel?

Dropped from my queue due to lack of response :(

Please resend when you get the chance, and address the above comment in
your changelog entry (and in your TODO file as well.)

thanks,

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/