From: Dan Carpenter <dan.carpenter@oracle.com>
To: Manavendra Nath Manav <mnm.kernel@gmail.com>
Cc: kernelnewbies@kernelnewbies.org, devel@driverdev.osuosl.org,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Why exported const value modified by another driver not updated in original driver
Date: Tue, 4 Sep 2012 05:25:44 -0700 [thread overview]
Message-ID: <20120904122544.GC19396@mwanda> (raw)
In-Reply-To: <CAJKgH8CNJM2SyR7bD8nXae13-Fq1MP1Xn7+383YU-HPwKBe+Zg@mail.gmail.com>
On Tue, Sep 04, 2012 at 03:58:20PM +0530, Manavendra Nath Manav wrote:
> Is the above a genuine kernel bug, or i am missing something out here. Pls help.
>
When you declare something as const then the compiler assumes it
really is const and uses a literal instead of reading from memory.
I'm surprised the compiler doesn't print a warning message.
It has to do with compilers, nothing to do with kernels.
regards,
dan carpenter
next prev parent reply other threads:[~2012-09-04 12:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 9:30 Why exported const value modified by another driver not updated in original driver Manavendra Nath Manav
2012-09-04 9:30 ` Manavendra Nath Manav
2012-09-04 10:28 ` Manavendra Nath Manav
2012-09-04 10:28 ` Manavendra Nath Manav
2012-09-04 10:39 ` Julian Andres Klode
2012-09-04 10:59 ` Manavendra Nath Manav
2012-09-04 10:59 ` Manavendra Nath Manav
2012-09-04 11:49 ` Chinmay V S
2012-09-04 12:25 ` Dan Carpenter [this message]
2012-09-05 8:27 ` Manavendra Nath Manav
2012-09-05 8:27 ` Manavendra Nath Manav
2012-09-04 10:46 ` Alan Cox
2012-09-04 10:46 ` Alan Cox
2012-09-04 12:06 ` Bernd Petrovitsch
2012-09-04 12:06 ` Bernd Petrovitsch
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=20120904122544.GC19396@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnm.kernel@gmail.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 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.