From: akpm@linux-foundation.org
To: siccegge@cs.fau.de, dhowells@redhat.com,
siccegge@stud.informatik.uni-erlangen.de,
mm-commits@vger.kernel.org
Subject: [merged] remove-redundant-check-for-config_mmu.patch removed from -mm tree
Date: Wed, 28 Apr 2010 11:03:21 -0400 [thread overview]
Message-ID: <201004281804.o3SI4s03010992@imap1.linux-foundation.org> (raw)
The patch titled
fs/binfmt_elf_fdpic.c: remove redundant check for CONFIG_MMU
has been removed from the -mm tree. Its filename was
remove-redundant-check-for-config_mmu.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: fs/binfmt_elf_fdpic.c: remove redundant check for CONFIG_MMU
From: Christoph Egger <siccegge@cs.fau.de>
The checks for CONFIG_MMU at this location are duplicated as all the code
is located inside a #ifndef CONFIG_MMU block. So the first conditional
block will always be included while the second never will.
Signed-off-by: Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/binfmt_elf_fdpic.c | 7 -------
1 file changed, 7 deletions(-)
diff -puN fs/binfmt_elf_fdpic.c~remove-redundant-check-for-config_mmu fs/binfmt_elf_fdpic.c
--- a/fs/binfmt_elf_fdpic.c~remove-redundant-check-for-config_mmu
+++ a/fs/binfmt_elf_fdpic.c
@@ -1005,15 +1005,8 @@ static int elf_fdpic_map_file_constdisp_
}
} else if (!mm->start_data) {
mm->start_data = seg->addr;
-#ifndef CONFIG_MMU
mm->end_data = seg->addr + phdr->p_memsz;
-#endif
}
reply other threads:[~2010-04-28 18:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004281804.o3SI4s03010992@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=siccegge@cs.fau.de \
--cc=siccegge@stud.informatik.uni-erlangen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox