* Using memcpy() in kernel space( driver)
@ 2006-05-04 6:05 rasmit.ranjan
2006-05-04 9:59 ` Pavel Machek
0 siblings, 1 reply; 2+ messages in thread
From: rasmit.ranjan @ 2006-05-04 6:05 UTC (permalink / raw)
To: linux-pm, linux-usb-devel, linux-kernel-digest
[-- Attachment #1.1: Type: text/plain, Size: 286 bytes --]
Hi all,
I am using memcpy() in my driver.
I am taking a spinlock and calling this function memcpy().
Is it safe to call memcpy() inside a lock?
If memcpy() fails, then will it create any problem in releasing the
spinlock ?
Please suggest.
Thanks and regards,
Rasmit.
[-- Attachment #1.2: Type: text/html, Size: 1362 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Using memcpy() in kernel space( driver)
2006-05-04 6:05 Using memcpy() in kernel space( driver) rasmit.ranjan
@ 2006-05-04 9:59 ` Pavel Machek
0 siblings, 0 replies; 2+ messages in thread
From: Pavel Machek @ 2006-05-04 9:59 UTC (permalink / raw)
To: rasmit.ranjan; +Cc: linux-kernel-digest, linux-pm, linux-usb-devel
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
On Thu 04-05-06 11:35:13, rasmit.ranjan@wipro.com wrote:
> Hi all,
> I am using memcpy() in my driver.
> I am taking a spinlock and calling this function memcpy().
> Is it safe to call memcpy() inside a lock?
> If memcpy() fails, then will it create any problem in releasing the
> spinlock ?
> Please suggest.
This is linux-PowerManagement, not linux-HELPME or linux-newbies list,
so this is offtopic here.
Uff, and your question certainly has nothing to do with usb. Pleasw
behave yourself.
Pavel
--
Thanks, Sharp!
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-05-04 9:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-04 6:05 Using memcpy() in kernel space( driver) rasmit.ranjan
2006-05-04 9:59 ` Pavel Machek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox