Re: Why exported const value modified by another driver not updated in original driver

On Tue, Sep 4, 2012 at 5:55 PM, Dan Carpenter wrote: > 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 comp

Re: Why exported const value modified by another driver not updated in original driver

On Tue, Sep 4, 2012 at 4:09 PM, Julian Andres Klode wrote: > On Tue, Sep 04, 2012 at 03:58:20PM +0530, Manavendra Nath Manav wrote: >> On Tue, Sep 4, 2012 at 3:00 PM, Manavendra Nath Manav >> wrote: >> > Hi, >> > >> > I have declared a static con

Re: Why exported const value modified by another driver not updated in original driver

On Tue, Sep 4, 2012 at 3:00 PM, Manavendra Nath Manav wrote: > Hi, > > I have declared a static const int variable in one driver and exported > that variable symbol. In another driver i am modifying that variable. > The other driver prints the modified value but the original drive

Why exported const value modified by another driver not updated in original driver

ot;static const volatile int" then the driver.ko prints modified value "987" during rmmod and the original value "123" is lost. What is the difference between this and previous declaration? Please forgive if you find this question silly? -- Manavendra Nath Manav -- To unsu