diff options
author | David S. Miller <davem@davemloft.net> | 2016-05-20 17:55:51 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-05-20 17:55:51 -0700 |
commit | 20c698d7791420fb242a0d49b80790fb2d951ace (patch) | |
tree | bcab1c55fa1ba86f09896f891663ad6cec062815 /drivers/sbus | |
parent | 33656a1f2ee5346c742d63ddd0e0970c95a56b70 (diff) | |
parent | 6b1cabe8992441afb542503781f11b9cce91e285 (diff) | |
download | linux-20c698d7791420fb242a0d49b80790fb2d951ace.tar.bz2 |
Merge branch 'sparc32-cosmetic-changes'
Sam Ravnborg says:
====================
sparc32: kgdb_32 and STRICT_MM_TYPECHECKS updates
A few cosmetic pathes for sparc32 follows.
I noticed some inconsistency in kgdb_32 that triggered a few patches.
The inconsistency in kgdb_32 turned out to have no functional impact.
But I anyway fixed it so kgdb_32 and kgdb_64 became just a tiny
bit more alike.
The STRICT_MM_TYPECHECKS patch was triggered by a
discussion on linux-arch where Arnd considered removing
this cruft.
The resulting benary of srmmu.c (I checked an assembler file)
was _smaller_ when I defined STRICT_MM_TYPECHECKS.
But due to lack of testing I left it undefined.
With the build errors fixed it should be trivial to
try out if defining STRICT_MM_TYPECHECKS breaks anything.
Any takers?
As I miss any working sparc32 gear for the moment this
has only been build tested - so please consider if it
is worth taking the risk to apply the patches.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/sbus')
0 files changed, 0 insertions, 0 deletions