public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: "Hebbar, Shivananda" <x0hebbar@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	Bhavin Shah <bshah@ti.com>, "Menon, Nishanth" <nm@ti.com>
Subject: Re: [Patchv2 0/8] DSPBRIDGE: typedef cleanup
Date: Tue, 23 Feb 2010 20:11:14 -0600	[thread overview]
Message-ID: <4B848AC2.9080506@ti.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E7394044A776231@dbde02.ent.ti.com>

On 2/5/2010 7:21 PM, Hebbar, Shivananda wrote:
> Resending the patches after updating review comments and also
> Fixing some compilation breaks.
>
> These patches remove the typedefs and replace it with normal C types:
>
> Shivananda Hebbar (8)
>
> DSPBRIDGE: typedef cleanup -DSP RTOS
> DSPBRIDGE: typedef cleanup -PROCTYPE
> DSPBRIDGE: typedef cleanup -PROCFAMILY
> DSPBRIDGE: typedef cleanup -DSP_HSTREAM
> DSPBRIDGE: typedef cleanup -DSP_HPROCESSOR
> DSPBRIDGE: typedef cleanup -DSP_HNODE
> DSPBRIDGE: typedef cleanup -BRD_STATUS
> DSPBRIDGE: typedef cleanup -CHNL_MODE
>
>   arch/arm/plat-omap/include/dspbridge/brddefs.h  |    1 -
>   arch/arm/plat-omap/include/dspbridge/chnldefs.h |    2 -
>   arch/arm/plat-omap/include/dspbridge/cmm.h      |    2 +-
>   arch/arm/plat-omap/include/dspbridge/dbdefs.h   |   18 +---
>   arch/arm/plat-omap/include/dspbridge/dispdefs.h |    4 +-
>   arch/arm/plat-omap/include/dspbridge/dmm.h      |    2 +-
>   arch/arm/plat-omap/include/dspbridge/drv.h      |    6 +-
>   arch/arm/plat-omap/include/dspbridge/node.h     |    4 +-
>   arch/arm/plat-omap/include/dspbridge/proc.h     |   43 +++++-----
>   arch/arm/plat-omap/include/dspbridge/wcdioctl.h |   96 +++++++++++-----------
>   arch/arm/plat-omap/include/dspbridge/wmd.h      |    4 +-
>   arch/arm/plat-omap/include/dspbridge/wmdchnl.h  |    2 +-
>   drivers/dsp/bridge/pmgr/cmm.c                   |    2 +-
>   drivers/dsp/bridge/pmgr/dev.c                   |    6 +-
>   drivers/dsp/bridge/pmgr/dmm.c                   |    2 +-
>   drivers/dsp/bridge/pmgr/wcd.c                   |    4 +-
>   drivers/dsp/bridge/rmgr/node.c                  |   12 ++--
>   drivers/dsp/bridge/rmgr/proc.c                  |   56 +++++++-------
>   drivers/dsp/bridge/rmgr/strm.c                  |    2 +-
>   drivers/dsp/bridge/wmd/chnl_sm.c                |    8 +-
>   drivers/dsp/bridge/wmd/tiomap3430.c             |    4 +-
>   21 files changed, 134 insertions(+), 146 deletions(-)
> --

Patch 5 had lots of checkpatch errors, I understand that they were there 
before but would be good if they are fixed when touching those lines 
(btw they were fixed). For this patch only one "suspect code indent" is 
still there because of the original code, it can't be fixed without 
changing a big chunk of the file so leaving it as it is (will be 
addressed by lindent)

Pushed to dspbridge

- omar

      parent reply	other threads:[~2010-02-24  2:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06  1:21 [Patchv2 0/8] DSPBRIDGE: typedef cleanup Hebbar, Shivananda
2010-02-06  9:22 ` Andy Shevchenko
2010-02-12 17:54   ` Hebbar, Shivananda
2010-02-24  2:11 ` 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=4B848AC2.9080506@ti.com \
    --to=omar.ramirez@ti.com \
    --cc=bshah@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=x0hebbar@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