summaryrefslogtreecommitdiffstats
path: root/fs/cifs/CHANGES
diff options
context:
space:
mode:
authorSteve French <sfrench@us.ibm.com>2009-01-12 21:03:25 +0000
committerSteve French <sfrench@us.ibm.com>2009-01-29 03:32:12 +0000
commit6a7f8d36c00ab7adef5fb633f7805c91e8c1e139 (patch)
tree9580a3e4fa4ec4f70a5f2a68b2a3d7ab52592ae8 /fs/cifs/CHANGES
parent0496e02d8791e7f06673a19a181be30dad6eff70 (diff)
downloadop-kernel-dev-6a7f8d36c00ab7adef5fb633f7805c91e8c1e139.zip
op-kernel-dev-6a7f8d36c00ab7adef5fb633f7805c91e8c1e139.tar.gz
[CIFS] Rename md5 functions to avoid collision with new rt modules
When rt modules were added they (each) included their own md5 with names which collided with the existing names of cifs's md5 functions. Renaming cifs's md5 modules so we don't collide with them. > Stephen Rothwell wrote: > When CIFS is built-in (=y) and staging/rt28[67]0 =y, there are multiple > definitions of: > > build-r8250.out:(.text+0x1d8ad0): multiple definition of `MD5Init' > build-r8250.out:(.text+0x1dbb30): multiple definition of `MD5Update' > build-r8250.out:(.text+0x1db9b0): multiple definition of `MD5Final' > > all of which need to have more unique identifiers for their global > symbols (e.g., rt28_md5_init, cifs_md5_init, foo, blah, bar). > CC: Greg K-H <gregkh@suse.de> Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'fs/cifs/CHANGES')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud