public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: shubhrajyoti@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2] McBSP: Fix the free variable update at remove.
Date: Tue, 2 Nov 2010 12:32:56 +0200	[thread overview]
Message-ID: <20101102123256.b6bee4b7.jhnikula@gmail.com> (raw)
In-Reply-To: <1288693488-10200-1-git-send-email-shubhrajyoti@ti.com>

On Tue,  2 Nov 2010 15:54:48 +0530
shubhrajyoti@ti.com wrote:

> From: Shubhrajyoti D <shubhrajyoti@ti.com>
> 
> At remove the free variable is wrongly updated.Attempting to solve the same.
> 
> Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
> ---
> -[v2] Instead of using 0/1 use a macro
> 
>  arch/arm/plat-omap/include/plat/mcbsp.h |    3 +++
>  arch/arm/plat-omap/mcbsp.c              |   10 +++++-----
>  2 files changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/arm/plat-omap/include/plat/mcbsp.h b/arch/arm/plat-omap/include/plat/mcbsp.h
> index b87d83c..8988733 100644
> --- a/arch/arm/plat-omap/include/plat/mcbsp.h
> +++ b/arch/arm/plat-omap/include/plat/mcbsp.h
> @@ -37,6 +37,9 @@ static struct platform_device omap_mcbsp##port_nr = {	\
>  	.id	= OMAP_MCBSP##port_nr,			\
>  }
>  
> +#define TRUE			1
> +#define FALSE			0
> +
Use 'true' & 'false' in the code instead and then there is no need to
redefine these. They are defined in include/linux/stddef.h which is
probably included already by some another file.


-- 
Jarkko

  reply	other threads:[~2010-11-02 10:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 10:24 [PATCH v2] McBSP: Fix the free variable update at remove shubhrajyoti
2010-11-02 10:32 ` Jarkko Nikula [this message]
2010-11-02 11:05   ` Datta, Shubhrajyoti
2010-11-02 10:34 ` Varadarajan, Charulatha
  -- strict thread matches above, loose matches on Subject: below --
2010-11-02 11:03 [PATCH v2 ] " shubhrajyoti
2010-11-03  9:28 ` Jarkko Nikula
2010-11-03  9:40   ` Datta, Shubhrajyoti

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=20101102123256.b6bee4b7.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=shubhrajyoti@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