mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Anton Blanchard <anton@samba.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Six archs are missing atomic_inc_return()
Date: Sat, 20 Nov 2004 21:18:35 +0100	[thread overview]
Message-ID: <20041120201835.GA1847@mail.13thfloor.at> (raw)
In-Reply-To: <200411181816_MC3-1-8EFB-D509@compuserve.com>

On Thu, Nov 18, 2004 at 06:14:06PM -0500, Chuck Ebbert wrote:
> Anton wrote:
> 
> > $ grep -l atomic_inc_return include/asm-*/atomic.h
> 
> 
>   I was assuming all archs used a macro for this, so I used:
> 
> $ grep 'define atomic_inc_return' asm-*/atomic.h
> 
> 
>   But your grep could have found this:
> 
>         /* FIXME: this arch does not have atomic_inc_return */
> 
> and returned a false positive.
> 
> 
>   What I need is a C-aware grep:
> 
> $ cgrep [--definition | --comment | --usage] atomic_inc_return asm-*/atomic.h
> 
> to search definitions, comments, and code body respectively.

what about cscope or c-tags?

best,
Herbert

> --Chuck Ebbert  18-Nov-04  18:08:49
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2004-11-20 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 23:14 Chuck Ebbert
2004-11-20 20:18 ` Herbert Poetzl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-18  6:44 Chuck Ebbert
2004-11-18  6:56 ` Anton Blanchard
2004-11-19  4:48 ` Andrew Morton
2004-11-19  6:16   ` David S. Miller

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=20041120201835.GA1847@mail.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=76306.1226@compuserve.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anton@samba.org \
    --cc=linux-kernel@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

Powered by JetHome