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: Wed, 12 Sep 2018 11:50:35 +0530	[thread overview]
Message-ID: <CAJd9=00U1MAb=Pb0UqNKWEhGL8z9gYnNgG7y=A3xH4cSN-dH9w@mail.gmail.com> (raw)

Hi All...
One curious question..

Linux Foundation tweeted this -
Meet Bhumika Goyal, age 22, from India. She has had more 340 patches
accepted into the Linux kernel, which helped her land one of our two Linux
Kernel Guru LiFT scholarships:
https://twitter.com/linuxfoundation/status/940340927897489408?lang=en

and her commits are -
https://github.com/torvalds/linux/commits?author=bhumikagoyal

One of my friend told me that, most/many of patches are just converting
variables to "*constant*"

For example - platform/chrome: chromeos_laptop: make chromeos_laptop const
-

Declare chromeos_laptop structures as *const *as they are only used during
a copy operation. As their value is never modified during runtime, they
can be made const.


the question is that, how these many const variable issues are left/missed
by the previous developers?!?! per my little knowledge, this task looks
like a simple one.. many other Kernel Developers should have thought and
made these changes long before, but i am not able to understand why this
wasnt done until recently?!?!?


-- 
Best Regards,
Sekar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180912/71c10aea/attachment.html>

             reply	other threads:[~2018-09-12  6:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12  6:20 inventsekar [this message]
2018-09-12  6:51 ` regarding const variables/structures 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
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=00U1MAb=Pb0UqNKWEhGL8z9gYnNgG7y=A3xH4cSN-dH9w@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.