kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: der.herr@hofr.at (Nicholas Mc Guire)
To: kernelnewbies@lists.kernelnewbies.org
Subject: regarding const variables/structures
Date: Thu, 13 Sep 2018 06:07:10 +0000	[thread overview]
Message-ID: <20180913060710.GA22373@osadl.at> (raw)
In-Reply-To: <CAJd9=01TXLnY9ZLOAK86cULMAJbKdimcDahvyS2uRPRKRuG2pA@mail.gmail.com>

On Thu, Sep 13, 2018 at 09:12:32AM +0530, inventsekar wrote:
> >>> A brute force grep in the kernel shows that there are 130493 " const "
> in there
> Hi Hofrat,
> 1. may i know the command to do this above grep please..

$ grep -cre " const " * | more

will give you the " const " count per file - and then put a shell loop around it

$ SUM=0 ; for N in `grep -cre " const " * | cut -f 2 -d ":" ` ; do let SUM=$SUM+$N ; done ; echo $SUM

...as noted "brute force"

> 2. (and the opposite) may i know the command to grep other type of
> variables/structures

well if you want to know how to do that then you do need to look at basics
if regular expressions are not clear then you might want to look at
those first. And grep really is not the right tool to search for specific
structures and their use use something like cscope.

Try to focus on doing work you understand including the tools and processes
around it - if you just are looking for a fast way of getting X patches
into the kernel you are wasting your time. What the work from Bhumika Goyal
shows is that its not about the complexity of the change but about the 
systematic approach based on using understanding a problem class, translating
it to an abstract representation amenable to tools (coccinelle in this case)
and documenting her understanding in the commit messages to each patch. 

thx!
hofrat 

  reply	other threads:[~2018-09-13  6:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12  6:20 regarding const variables/structures inventsekar
2018-09-12  6:51 ` Greg KH
2018-09-12  7:08 ` Nicholas Mc Guire
2018-09-12 17:10   ` inventsekar
2018-09-12 17:53     ` valdis.kletnieks at vt.edu
2018-09-12 18:23       ` inventsekar
2018-09-13  9:50         ` Tobin C. Harding
2018-09-14 19:49           ` inventsekar
2018-09-17  7:29             ` Shakthi Kannan
2018-09-18  5:46               ` inventsekar
2018-09-17 15:00             ` valdis.kletnieks at vt.edu
2018-09-13  3:42   ` inventsekar
2018-09-13  6:07     ` Nicholas Mc Guire [this message]
2018-09-14 19:52       ` inventsekar
2018-09-14 22:09         ` Kenneth Adam 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=20180913060710.GA22373@osadl.at \
    --to=der.herr@hofr.at \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).