Re: void __iomem *addr should be const

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Subject: Re: void __iomem *addr should be const
From: Hugo Lefeuvre <hle@xxxxxxxxxx>
Date: Sat, 16 Feb 2019 21:49:21 +0100
Cc: Arnd Bergmann <arnd@xxxxxxxx>, linux-arch@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.21.1902162016000.1683@nanos.tec.linutronix.de>
References: <20190210122903.GA2400@behemoth.owl.eu.com.local> <alpine.DEB.2.21.1902162016000.1683@nanos.tec.linutronix.de>
User-agent: Mutt/1.10.1 (2018-07-13)

Hi,

> The const makes perfectly sense and we should have consistent state all
> over the place.

Thanks, I will submit a patch addressing this issue soon.

regards,
 Hugo

-- 
                Hugo Lefeuvre (hle)    |    www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C

References:
- void __iomem *addr should be const
  - From: Hugo Lefeuvre
- Re: void __iomem *addr should be const
  - From: Thomas Gleixner

Prev by Date: Re: void __iomem *addr should be const
Next by Date: Re: [GIT PULL V3] csky fixes for v5.0-rc6
Previous by thread: Re: void __iomem *addr should be const
Next by thread: [PATCH] locking/rwsem: Remove arch specific rwsem files
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Newbies] [x86 Platform Driver] [Netdev] [Linux Wireless] [Netfilter] [Bugtraq] [Linux Filesystems] [Yosemite Discussion] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper]

Powered by Linux