From: Nishanth Menon <nm@ti.com>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Hiroshi Doyu <Hiroshi.DOYU@nokia.com>,
Ameya Palande <ameya.palande@nokia.com>,
Felipe Contreras <felipe.contreras@nokia.com>,
"Guzman Lugo, Fernando" <x0095840@ti.com>,
"Ramos Falcon, Ernesto" <ernesto@ti.com>
Subject: Re: [PATCH 4/8] DSPBRIDGE: Remove unused hDrvObject in bridge_[open|release]
Date: Fri, 8 Jan 2010 15:37:47 -0600 [thread overview]
Message-ID: <4B47A5AB.6080001@ti.com> (raw)
In-Reply-To: <27F9C60D11D683428E133F85D2BB4A53042DC955C1@dlee03.ent.ti.com>
Ramirez Luna, Omar had written, on 01/08/2010 03:29 PM, the following:
>> From: Menon, Nishanth
>>
>> Omar Ramirez Luna had written, on 01/07/2010 07:00 PM, the following:
>>> This patch removes an unused variable in bridge_open
>>> and bridge_release functions, which reduces indentation.
>>>
>>> Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com>
>>> ---
>>> drivers/dsp/bridge/rmgr/drv_interface.c | 25 +++++--------------------
>>> 1 files changed, 5 insertions(+), 20 deletions(-)
>>>
>>> diff --git a/drivers/dsp/bridge/rmgr/drv_interface.c b/drivers/dsp/bridge/rmgr/drv_interface.c
>>> index 3a4d058..e551840 100644
>>> --- a/drivers/dsp/bridge/rmgr/drv_interface.c
>>> +++ b/drivers/dsp/bridge/rmgr/drv_interface.c
>>> @@ -540,18 +540,10 @@ static void __exit bridge_exit(void)
>>> static int bridge_open(struct inode *ip, struct file *filp)
>>> {
>>> int status = 0;
>>> - DSP_STATUS dsp_status;
>>> - HANDLE hDrvObject;
>>> struct PROCESS_CONTEXT *pr_ctxt = NULL;
>>>
>>> GT_0trace(driverTrace, GT_ENTER, "-> bridge_open\n");
>>>
>>> - dsp_status = CFG_GetObject((u32 *)&hDrvObject, REG_DRV_OBJECT);
>>> - if (DSP_FAILED(dsp_status)) {
>> is this some sort of verification if the hDrvObject is valid?
>> if so this is not an unused variable rt?
>
> No, this drv object was used for inserting and removing the process
> context, it doesn't work as validation at least not in this place.
thanks.
Acked-by: Nishanth Menon <nm@ti.com>
>
>>> - status = -EIO;
>>> - goto err;
>>> - }
>>> -
>>> /*
>>> * Allocate a new process context and insert it into global
>>> * process context list.
>>> @@ -564,7 +556,6 @@ static int bridge_open(struct inode *ip, struct file *filp)
>>>
>>> filp->private_data = pr_ctxt;
>>>
>>> -err:
>>> GT_0trace(driverTrace, GT_ENTER, "<- bridge_open\n");
>>> return status;
>>> }
>>> @@ -576,8 +567,6 @@ err:
>>> static int bridge_release(struct inode *ip, struct file *filp)
>>> {
>>> int status = 0;
>>> - DSP_STATUS dsp_status;
>>> - HANDLE hDrvObject;
>>> struct PROCESS_CONTEXT *pr_ctxt;
>>>
>>> GT_0trace(driverTrace, GT_ENTER, "-> bridge_release\n");
>>> @@ -588,15 +577,11 @@ static int bridge_release(struct inode *ip, struct file *filp)
>>> }
>>>
>>> pr_ctxt = filp->private_data;
>>> - dsp_status = CFG_GetObject((u32 *)&hDrvObject, REG_DRV_OBJECT);
>>> - if (DSP_SUCCEEDED(dsp_status)) {
>> is this some sort of verification if the hDrvObject is valid?
>> if so this is not an unused variable rt?
>
> No, this drv object was used for inserting and removing the process
> context, it doesn't work as validation at least not in this place.
>
>>> - flush_signals(current);
>>> - DRV_RemoveAllResources(pr_ctxt);
>>> - PROC_Detach(pr_ctxt);
>>> - MEM_Free(pr_ctxt);
>>> - } else {
>>> - status = -EIO;
>>> - }
>>> + flush_signals(current);
>>> + DRV_RemoveAllResources(pr_ctxt);
>>> + PROC_Detach(pr_ctxt);
>>> + MEM_Free(pr_ctxt);
>>> +
>>> filp->private_data = NULL;
>>>
>>> err:
>
> - omar
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2010-01-08 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 1:00 [PATCH 4/8] DSPBRIDGE: Remove unused hDrvObject in bridge_[open|release] Omar Ramirez Luna
2010-01-08 2:19 ` Nishanth Menon
2010-01-08 21:29 ` Ramirez Luna, Omar
2010-01-08 21:37 ` Nishanth Menon [this message]
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=4B47A5AB.6080001@ti.com \
--to=nm@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=ernesto@ti.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@ti.com \
--cc=x0095840@ti.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