From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: gorcunov@gmail.com, mingo@elte.hu, tglx@linutronix.de
Subject: + ia32-emu-remove-dead-code.patch added to -mm tree
Date: Mon, 12 Nov 2007 18:15:12 -0800 [thread overview]
Message-ID: <200711130215.lAD2FCCW021508@imap1.linux-foundation.org> (raw)
The patch titled
ia32-emu: remove dead code
has been added to the -mm tree. Its filename is
ia32-emu-remove-dead-code.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: ia32-emu: remove dead code
From: Cyrill Gorcunov <gorcunov@gmail.com>
Remove useless second time checking of fsave argument in save_i387_ia32()
routine. It's possible the compiler is doing the same but that is much
better to remove the dead code explicitly.
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/x86/ia32/fpu32.c | 2 --
1 file changed, 2 deletions(-)
diff -puN arch/x86/ia32/fpu32.c~ia32-emu-remove-dead-code arch/x86/ia32/fpu32.c
--- a/arch/x86/ia32/fpu32.c~ia32-emu-remove-dead-code
+++ a/arch/x86/ia32/fpu32.c
@@ -174,8 +174,6 @@ int save_i387_ia32(struct task_struct *t
if (fsave)
return 0;
err |= __put_user(tsk->thread.i387.fxsave.swd, &buf->status);
- if (fsave)
- return err ? -1 : 1;
err |= __put_user(X86_FXSR_MAGIC, &buf->magic);
err |= __copy_to_user(&buf->_fxsr_env[0], &tsk->thread.i387.fxsave,
sizeof(struct i387_fxsave_struct));
_
Patches currently in -mm which might be from gorcunov@gmail.com are
git-cifs.patch
ia32-emu-remove-dead-code.patch
reply other threads:[~2007-11-13 2:15 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=200711130215.lAD2FCCW021508@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.