<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 8, 2014 at 10:08 PM, Greg Kroah-Hartman <span dir="ltr"><<a href="mailto:greg@kroah.com" target="_blank">greg@kroah.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
A: No.<br>
Q: Should I include quotations after my reply?<br>
<br>
<a href="http://daringfireball.net/2007/07/on_top" target="_blank">http://daringfireball.net/2007/07/on_top</a><br>
<span class=""><br>
On Wed, Oct 08, 2014 at 10:01:43PM +0530, Jeshwanth Kumar N K wrote:<br>
> Greg, then what will you suggest for my case? I mean any alternative ?<br>
<br>
</span>What "case"? What problem are you trying to solve?<br>
<br>
greg k-h<br>
</blockquote></div><br><br clear="all"></div><div class="gmail_extra">Oh, correct. 2nd time I am warned on this (may be practise by using outlook). Will reply bottom now onwards - sorry.<br><br></div><div class="gmail_extra">My case was: I have a hall sensor connected to Beaglebone black, And Userspace needed a wakeup once the interrupt occur (example: every rising edge of GPIO). Before that, the program will register (ioctl) the User space task pointer with my kernel module, then my kernel module start sending signal for every interrupt occur. We can consider roughly around 100 to 200 interrupts per second maximum. ( I have not done this, but may be we can consider kernel will get notified when userspace program stops. so that it will not send any signal). So for this case, any other alternative implementation ?<br><br></div><div class="gmail_extra">Thanks <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">-- <br><div dir="ltr"><div>Regards<br>Jeshwanth Kumar N K<br></div>Bangalore, India<br></div>
</div></div>