All of lore.kernel.org
 help / color / mirror / Atom feed
From: inventsekar@gmail.com (inventsekar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: regarding const variables/structures
Date: Sat, 15 Sep 2018 01:22:07 +0530	[thread overview]
Message-ID: <CAJd9=037Tmv7nVS7oquDKBzUahSJPzqEi7GGXmf3Ak6z9Z2N3Q@mail.gmail.com> (raw)
In-Reply-To: <20180913060710.GA22373@osadl.at>

Hi, for the past three years I have been trying hard to do Linux kernel
development, but, with No success.

I don't know what is the exact reason...maybe, I didn't do much practical,
all the times I was only reading reading reading... so you can understand
my frustration, that I wanted to submit my first patch asap...and then
slowly I can do concentrate on other areas of kernel development... ok
thank you.

On Thu 13 Sep, 2018, 11:37 AM Nicholas Mc Guire, <der.herr@hofr.at> wrote:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180915/817f6b22/attachment.html>

  reply	other threads:[~2018-09-14 19:52 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
2018-09-14 19:52       ` inventsekar [this message]
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='CAJd9=037Tmv7nVS7oquDKBzUahSJPzqEi7GGXmf3Ak6z9Z2N3Q@mail.gmail.com' \
    --to=inventsekar@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.