On Mon, 2015-01-26 at 00:39 -0500, devendra.aaru wrote:
> Hello,
>
> Sorry for the late reply.
>
> Would reverting last two patches help ?
>
> Thanks,
> Devendra
Devendra,
I am really sorry for how long this is taking. I don't think that
there's anything wrong with your patches, but rather th
On Wed, Jan 21, 2015 at 1:12 PM, Romer, Benjamin M
wrote:
> Hi,
>
> I've built and tested your set of patches on an s-Par guest, and with
> the changes I get a kernel oops during boot, but I haven't determined
> the cause yet. I'll let you know what I find. :)
>
> -- Ben
>
Hello,
Sorry for the l
On Wed, 2015-01-21 at 04:03 -0500, Devendra Naga wrote:
> The 1st patch (replace kthread_create..) replace the
> kthread_create and wake_up_process with a call to
> kthread_run.
>
> The 2nd patch changes the library API uisthread_start
> and uisthread_stop to use the kthread API.
>
> The 3rd patc
The 1st patch (replace kthread_create..) replace the
kthread_create and wake_up_process with a call to
kthread_run.
The 2nd patch changes the library API uisthread_start
and uisthread_stop to use the kthread API.
The 3rd patch and 4th patch checks on kthread_should_stop
instead of checking should
Oops, I have forgotten the RFC before the patches from 1 to 5 also i
have missed two email addresses (i have added them now). I will resend
the whole series again with RFC tag before each PATCH and also proper
cc's.
Sorry
On Wed, Jan 21, 2015 at 3:55 AM, Devendra Naga wrote:
> The 1st patch (rep
The 1st patch (replace kthread_create..) replace the
kthread_create and wake_up_process with a call to
kthread_run.
The 2nd patch changes the library API uisthread_start
and uisthread_stop to use the kthread API.
The 3rd patch and 4th patch checks on kthread_should_stop
instead of checking should
