From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: mikey@neuling.org, anton@samba.org, shuahkh@osg.samsung.com,
mpe@ellerman.id.au
Subject: [PATCH V5 02/13] powerpc, process: Remove the unused extern dscr_default
Date: Thu, 21 May 2015 12:13:02 +0530 [thread overview]
Message-ID: <1432190593-17253-3-git-send-email-khandual@linux.vnet.ibm.com> (raw)
In-Reply-To: <1432190593-17253-1-git-send-email-khandual@linux.vnet.ibm.com>
The process context switch code no longer uses dscr_default variable
from the sysfs.c file. The variable became unused when we started
storing the CPU specific DSCR value in the PACA structure instead.
This patch just removes this extern declaration. It was originally
added by the following commit.
efcac658: powerpc: Per process DSCR + some fixes (try#4)
Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
---
arch/powerpc/kernel/process.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
index febb50d..8005e18 100644
--- a/arch/powerpc/kernel/process.c
+++ b/arch/powerpc/kernel/process.c
@@ -1112,7 +1112,6 @@ static void setup_ksp_vsid(struct task_struct *p, unsigned long sp)
/*
* Copy a thread..
*/
-extern unsigned long dscr_default; /* defined in arch/powerpc/kernel/sysfs.c */
/*
* Copy architecture-specific thread state
--
2.1.0
next prev parent reply other threads:[~2015-05-21 6:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 6:43 [PATCH V5 00/13] POWER DSCR fixes, improvements, docs and tests Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 01/13] powerpc: Fix handling of DSCR related facility unavailable exception Anshuman Khandual
2015-05-21 6:43 ` Anshuman Khandual [this message]
2015-05-21 6:43 ` [PATCH V5 03/13] powerpc, offset: Change PACA_DSCR to PACA_DSCR_DEFAULT Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 04/13] powerpc, dscr: Added some in-code documentation Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 05/13] documentation, powerpc: Add documentation for DSCR support Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 06/13] selftests, powerpc: Add test for system wide DSCR default Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 07/13] selftests, powerpc: Add test for explicitly changing DSCR value Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 08/13] selftests, powerpc: Add test for DSCR SPR numbers Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 09/13] selftests, powerpc: Add test for DSCR value inheritence across fork Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 10/13] selftests, powerpc: Add test for DSCR inheritence across fork & exec Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 11/13] selftests, powerpc: Add test for all DSCR sysfs interfaces Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 12/13] selftests, powerpc: Add thread based stress test for " Anshuman Khandual
2015-06-03 8:44 ` Anshuman Khandual
2015-05-21 6:43 ` [PATCH V5 13/13] selftests, powerpc: Add gitignore file for the new DSCR tests Anshuman Khandual
2015-05-25 8:38 ` [PATCH V5 00/13] POWER DSCR fixes, improvements, docs and tests Anshuman Khandual
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=1432190593-17253-3-git-send-email-khandual@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=shuahkh@osg.samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).