diff options
| author | Christoph Hellwig <hch@lst.de> | 2019-06-13 09:09:02 +0200 |
|---|---|---|
| committer | Greg Ungerer <gerg@kernel.org> | 2019-06-24 01:16:47 +0200 |
| commit | a2357223c50a784ae144c8398683551252bcd61d (patch) | |
| tree | d5ea178771a9f356b6660235a3c2682a0d7eba42 /arch/riscv/Kconfig | |
| parent | binfmt_flat: move the MAX_SHARED_LIBS definition to binfmt_flat.c (diff) | |
| download | linux-a2357223c50a784ae144c8398683551252bcd61d.tar.xz linux-a2357223c50a784ae144c8398683551252bcd61d.zip | |
binfmt_flat: don't offset the data start
Ever since the initial commit of the binfmt_flat shared library
support back in the bitkeeper days we've offset the actual in-memory
.data start by one field per possible shared library, or 1 in case
shared library support isn't enabled. I can't find anything in the
loader that actually makes use of it, nor was it present before
shared library support it.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
Diffstat (limited to 'arch/riscv/Kconfig')
0 files changed, 0 insertions, 0 deletions