public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	Ameya Palande <ameya.palande@nokia.com>
Subject: Re: [PATCH 00/10] dsp-bridge: deh: general cleanups
Date: Mon, 19 Apr 2010 15:37:28 -0500	[thread overview]
Message-ID: <4BCCBF08.6030909@ti.com> (raw)
In-Reply-To: <i2x94a0d4531004150512qf66c7c42u160707e3a89ec39a@mail.gmail.com>

On 4/15/2010 7:12 AM, Felipe Contreras wrote:
> On Wed, Mar 24, 2010 at 12:25 AM, Felipe Contreras
> <felipe.contreras@gmail.com>  wrote:
>> While trying to fix the recovery feature I stumbled many areas of improvments
>> in 'deh' (whatever that means).
>>
>> I quickly tested tesed these changes in Nokia hw, there should be essentially
>> no functional changes.
>>
>> Cheers.
>>
>> Felipe Contreras (10):
>>   dsp-bridge: deh: remove obvious comments
>>   dsp-bridge: deh: trivial cleanups
>>   dsp-bridge: deh: remove unnecessary casts
>>   dsp-bridge: deh: improve logging stuff
>>   dsp-bridge: deh: report mmu faults as errors
>>   dsp-bridge: deh: decrease nesting levels
>>   dsp-bridge: deh: fix obvious return codes
>>   dsp-bridge: deh: reorganize create()
>>   dsp-bridge: deh: fix hdeh_mgr silliness
>>   dsp-bridge: deh: fix dummy_va_addr
>>
>>   arch/arm/plat-omap/include/dspbridge/wmddeh.h |   24 +-
>>   drivers/dsp/bridge/wmd/ue_deh.c               |  392 +++++++++++--------------
>>   2 files changed, 191 insertions(+), 225 deletions(-)
>
> I guess these patches don't apply any more. Shall I rebase them? If so... where?

As noted in a private mail, your patches were rebased and now pushed to 
dspbridge.

Only this patch was dropped "dsp-bridge: deh: trivial cleanups"[1]

I removed the trivial checkpatch warnings (80 char limit and space after 
comma) from 2 of them.

Omar

---
[1] http://marc.info/?l=linux-omap&m=126938906708916&w=2

      reply	other threads:[~2010-04-19 20:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 21:25 [PATCH 00/10] dsp-bridge: deh: general cleanups Felipe Contreras
2010-03-23 21:25 ` [PATCH 01/10] dsp-bridge: deh: remove obvious comments Felipe Contreras
2010-03-23 21:25 ` [PATCH 02/10] dsp-bridge: deh: trivial cleanups Felipe Contreras
2010-03-24  0:04   ` Omar Ramirez Luna
2010-03-23 21:25 ` [PATCH 03/10] dsp-bridge: deh: remove unnecessary casts Felipe Contreras
2010-03-23 21:25 ` [PATCH 04/10] dsp-bridge: deh: improve logging stuff Felipe Contreras
2010-03-23 21:25 ` [PATCH 05/10] dsp-bridge: deh: report mmu faults as errors Felipe Contreras
2010-03-23 21:25 ` [PATCH 06/10] dsp-bridge: deh: decrease nesting levels Felipe Contreras
2010-03-23 21:25 ` [PATCH 07/10] dsp-bridge: deh: fix obvious return codes Felipe Contreras
2010-03-23 21:25 ` [PATCH 08/10] dsp-bridge: deh: reorganize create() Felipe Contreras
2010-03-23 21:25 ` [PATCH 09/10] dsp-bridge: deh: fix hdeh_mgr silliness Felipe Contreras
2010-03-23 21:25 ` [PATCH 10/10] dsp-bridge: deh: fix dummy_va_addr Felipe Contreras
2010-04-15 12:12 ` [PATCH 00/10] dsp-bridge: deh: general cleanups Felipe Contreras
2010-04-19 20:37   ` Omar Ramirez Luna [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=4BCCBF08.6030909@ti.com \
    --to=omar.ramirez@ti.com \
    --cc=ameya.palande@nokia.com \
    --cc=felipe.contreras@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    /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