From: Nishanth Menon <nm@ti.com>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
linux-omap <linux-omap@vger.kernel.org>,
Hiroshi Doyu <Hiroshi.DOYU@nokia.com>
Subject: Re: [PATCH 0/9] dspbridge cleanup patches
Date: Wed, 25 Nov 2009 15:56:55 -0600 [thread overview]
Message-ID: <4B0DA827.4090900@ti.com> (raw)
In-Reply-To: <27F9C60D11D683428E133F85D2BB4A530426F26833@dlee03.ent.ti.com>
Ramirez Luna, Omar had written, on 11/25/2009 03:52 PM, the following:
>> From: Menon, Nishanth
>> Subject: Re: [PATCH 0/9] dspbridge cleanup patches
>>
>>> 1. http://dev.omapzoom.org/?p=tidspbridge/kernel-
>> dspbridge.git;a=commit;h=b6b7bc5b620596790b2ea26225908b3cf62c36be
>>
>> How about the discussion in
>> http://marc.info/?l=linux-omap&m=123728293826758&w=2 ?
>> same arguments seem valid now..
>>
>
> Opps, sorry about that, seems like I stole/redid your patch Felipe, I'll diff it (to see nothing is missing), fix author and add my signed off.
>
> Nishant,
>
> I actually removed the history because one of your comments:
> [snip]
>>> + * GPIO Module disable when not in use - Charulatha V
>>> + <charu@ti.com>
>> Please stop adding history here.. git commit is supposed to contain
>> it. No stats are generated from looking at file history anymore and
>> there is definitely the risk of getting as big as
>> http://dev.omapzoom.org/?p=tidspbridge/kernel-
>> dspbridge.git;a=blob;f=drivers/dsp/bridge/rmgr/mgr.c;h=943cf932a35b75f
>> 709f
>> 554deb3c51c47088d8b78;hb=refs/heads/dspbridge#l26
> [snip]
lets not mix things up. GPIO does not come with the legacy burden of 10
years that DSPBridge has.
http://marc.info/?l=linux-omap&m=123729745613662&w=2 summarizes my views
on DSPBridge.
>
> Personally, If any folk mentioned on the removed history disagrees, it is welcome to send a
> mail to this mailing list detailing his contributions and I guess
someone (me, most likely)
>will check on it. For now a line thanking "vp", "rr", "sp" etc. for
their initial work will be added to the patch.
I doubt if many folks even are there on the linux-omap mailing list..
might be good for us to check OR at least note:
Anonymous contributors (vp,vr etc..).. I think this was previously
discussed in the chain.
>
>>> 3. http://dev.omapzoom.org/?p=tidspbridge/kernel-
>> dspbridge.git;a=commit;h=b4d73d15bd2b1c7dd1cc89ca9e81a98946ddf241
>> printk(KERN_ERR ?? why not use the pr_err/warning/info family?
>>
>
> My git:
> drivers/dsp/bridge/rmgr/dbdcd.c | 165 +++-----
> drivers/dsp/bridge/rmgr/disp.c | 254 ++++-------
> drivers/dsp/bridge/rmgr/drv.c | 399 +++++++----------
> drivers/dsp/bridge/rmgr/drv_interface.c | 92 ++---
> drivers/dsp/bridge/rmgr/dspdrv.c | 34 +-
> drivers/dsp/bridge/rmgr/proc.c | 754 ++++++++++++++-----------------
> drivers/dsp/bridge/rmgr/rmm.c | 46 +--
> drivers/dsp/bridge/rmgr/strm.c | 144 +++----
> 8 files changed, 791 insertions(+), 1097 deletions(-)
>
> (now): Removing GT_Trace wrappers and replacing for pr_debug
Throughout please.. no more printks.. thanks..
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-11-25 21:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 0:50 [PATCH 0/9] dspbridge cleanup patches Omar Ramirez Luna
[not found] ` <1259023830-7557-2-git-send-email-omar.ramirez@ti.com>
2009-11-24 0:50 ` [PATCH 2/9] DSPBRIDGE: trivial checkpatch fixes Omar Ramirez Luna
[not found] ` <1259023830-7557-4-git-send-email-omar.ramirez@ti.com>
2009-11-24 0:50 ` [PATCH 4/9] DSPBRIDGE: Use _IOxx macro to define ioctls Omar Ramirez Luna
2009-11-24 0:50 ` [PATCH 5/9] DSPBRIDGE: trivial cleanup and indentation for io_sm Omar Ramirez Luna
2009-11-24 0:50 ` [PATCH 6/9] DSPBRIDGE: Remove DPC, create, destroy and schedule wrappers Omar Ramirez Luna
2009-11-24 0:50 ` [PATCH 7/9] DSPBRIDGE: Remove main DPC wrapper for IO and MMUfault Omar Ramirez Luna
2009-11-24 0:50 ` [PATCH 8/9] DSPBRIDGE: Remove DPC module from SERVICES layer Omar Ramirez Luna
2009-11-24 0:50 ` [PATCH 9/9] DSPBRIDGE: Remove DPC object structure Omar Ramirez Luna
2009-11-25 22:38 ` [PATCH 7/9] DSPBRIDGE: Remove main DPC wrapper for IO and MMUfault Nishanth Menon
2009-11-25 19:17 ` [PATCH 6/9] DSPBRIDGE: Remove DPC, create, destroy and schedule wrappers Felipe Balbi
2009-11-25 19:44 ` Ramirez Luna, Omar
2009-11-25 22:34 ` Nishanth Menon
2009-11-25 23:05 ` Ramirez Luna, Omar
2009-11-25 19:15 ` [PATCH 5/9] DSPBRIDGE: trivial cleanup and indentation for io_sm Felipe Balbi
2009-11-25 19:47 ` Ramirez Luna, Omar
2009-11-26 5:47 ` Artem Bityutskiy
2009-11-25 21:53 ` Nishanth Menon
2009-11-25 21:51 ` [PATCH 4/9] DSPBRIDGE: Use _IOxx macro to define ioctls Nishanth Menon
2009-11-25 21:37 ` [PATCH 2/9] DSPBRIDGE: trivial checkpatch fixes Nishanth Menon
2009-11-25 21:56 ` Ramirez Luna, Omar
2009-11-26 7:30 ` Hiroshi DOYU
2009-11-24 6:54 ` [PATCH 0/9] dspbridge cleanup patches Artem Bityutskiy
2009-11-25 17:32 ` Felipe Contreras
2009-11-25 20:49 ` Ramirez Luna, Omar
2009-11-25 20:56 ` Nishanth Menon
2009-11-25 21:52 ` Ramirez Luna, Omar
2009-11-25 21:56 ` Nishanth Menon [this message]
2009-11-26 13:40 ` Felipe Contreras
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=4B0DA827.4090900@ti.com \
--to=nm@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=dedekind1@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@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