From: Rupesh Gujare <rupesh.gujare@atmel.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: <devel@linuxdriverproject.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 4/4] staging: ozwpan: Create deferred work to destroy PD object.
Date: Fri, 23 Aug 2013 11:38:01 +0100 [thread overview]
Message-ID: <52173B89.7070607@atmel.com> (raw)
In-Reply-To: <52164E53.9000700@cogentembedded.com>
On 22/08/13 18:45, Sergei Shtylyov wrote:
>> +void oz_pd_destroy(struct oz_pd *pd)
>> +{
>> + int ret;
>> +
>> + if (hrtimer_active(&pd->timeout))
>> + hrtimer_cancel(&pd->timeout);
>> + if (hrtimer_active(&pd->heartbeat))
>> + hrtimer_cancel(&pd->heartbeat);
>> +
>> + memset(&pd->workitem, 0, sizeof(pd->workitem));
>> + INIT_WORK(&pd->workitem, oz_pd_free);
>
> Hm, memset(), then INIT_WORK()? Is memset() necessary?
Opps.. you are right, I think we don't need memset() here.
>
>> + ret = schedule_work(&pd->workitem);
>> +
>
> Don't think empty line is needed here.
Yes, I agree. I will send follow on patches to fix this, as original
patches had already been applied by Greg.
>
>> + if (ret)
>> + oz_pd_dbg(pd, ON, "failed to schedule workitem\n");
>> +}
>> +
>> +/*------------------------------------------------------------------------------
>>
>> * Context: softirq-serialized
>> */
>> int oz_services_start(struct oz_pd *pd, u16 apps, int resume)
>> diff --git a/drivers/staging/ozwpan/ozpd.h
>> b/drivers/staging/ozwpan/ozpd.h
>> index 996ef65..12c7129 100644
>> --- a/drivers/staging/ozwpan/ozpd.h
>> +++ b/drivers/staging/ozwpan/ozpd.h
>> @@ -99,6 +99,7 @@ struct oz_pd {
>> u8 timeout_type;
>> struct tasklet_struct heartbeat_tasklet;
>> struct tasklet_struct timeout_tasklet;
>> + struct work_struct workitem;
>
> Er, other field names seem aligned, what about this one?
>
After applying patch, it looks all right to me.
--
Regards,
Rupesh Gujare
next prev parent reply other threads:[~2013-08-23 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 16:38 [PATCH 1/4] ozwpan: staging: Fix crash for race condition Rupesh Gujare
2013-08-22 16:38 ` [PATCH 2/4] staging: ozwpan: Check error condition before creating endpoint Rupesh Gujare
2013-08-22 16:38 ` [PATCH 3/4] staging: ozwpan: Increment reference counter Rupesh Gujare
2013-08-22 16:38 ` [PATCH 4/4] staging: ozwpan: Create deferred work to destroy PD object Rupesh Gujare
2013-08-22 17:45 ` Sergei Shtylyov
2013-08-23 10:38 ` Rupesh Gujare [this message]
2013-08-23 9:05 ` Dan Carpenter
2013-08-23 11:18 ` Rupesh Gujare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52173B89.7070607@atmel.com \
--to=rupesh.gujare@atmel.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome