From: Ameya Palande <ameya.palande@nokia.com>
To: "Contreras Felipe (Nokia-D/Helsinki)" <felipe.contreras@nokia.com>
Cc: "ext Guzman Lugo, Fernando" <x0095840@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Menon, Nishanth" <nm@ti.com>,
"Chitriki Rudramuni, Deepak" <deepak.chitriki@ti.com>,
"Ramirez Luna, Omar" <omar.ramirez@ti.com>
Subject: Re: [PATCHv4 4/4] DSPBRIDGE: Improved mapped memory cleanup
Date: Thu, 18 Feb 2010 16:47:28 +0200 [thread overview]
Message-ID: <1266504448.2105.12.camel@sanganak> (raw)
In-Reply-To: <20100218142728.GD4097@annwn.felipec.org>
Hi Felipe,
On Thu, 2010-02-18 at 15:27 +0100, Contreras Felipe (Nokia-D/Helsinki)
wrote:
> On Thu, Feb 18, 2010 at 01:15:55PM +0100, Ameya Palande wrote:
> > On Thu, 2010-02-18 at 02:52 +0100, ext Guzman Lugo, Fernando wrote:
> > > What do you think about it?
> > > Instead of removing DRV_InsertDMMResElement make it an inline function with your code inside:
> >
> > Making DRV_InsertDMMResElement inline doesn't make sense since we are
> > not calling it multiple times.
>
> I agree with Fernando; the code would be more readable. Even more if we
> rename the function to instert_map_element().
I guess the issue is about why this code is doing it rather than the
readability of code. I have sent V5 of the patchset with comment
explaining the purpose of doing this.
If you think that by creating a new static inline function like
insert_map_element(), we can understand it better then following comment
also does the same thing:
/* Following code inserts a map element ... and explain why */
Anyways insert_map_element() function doesn't explain why it is
required :(
Cheers,
Ameya.
prev parent reply other threads:[~2010-02-18 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 18:05 [PATCHv4 0/4] DSPBRIDGE: Improved reserved and mapped resource cleanup Ameya Palande
2010-02-17 18:05 ` [PATCHv4 1/4] DSPBRIDGE: Rename DMM_RES_OBJECT to DMM_MAP_OBJECT Ameya Palande
2010-02-17 18:05 ` [PATCHv4 2/4] DSPBRIDGE: New reserved memory accounting framework Ameya Palande
2010-02-18 1:40 ` Guzman Lugo, Fernando
2010-02-18 14:48 ` Ameya Palande
2010-02-17 18:05 ` [PATCHv4 3/4] DSPBRIDGE: Fix memory corruption in DRV_ProcFreeDMMRes Ameya Palande
2010-02-17 18:05 ` [PATCHv4 4/4] DSPBRIDGE: Improved mapped memory cleanup Ameya Palande
2010-02-18 1:52 ` Guzman Lugo, Fernando
2010-02-18 12:15 ` Ameya Palande
2010-02-18 14:27 ` Felipe Contreras
2010-02-18 14:47 ` Ameya Palande [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=1266504448.2105.12.camel@sanganak \
--to=ameya.palande@nokia.com \
--cc=deepak.chitriki@ti.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--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