From: Ingo Molnar <mingo@kernel.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mundt <paul.mundt@gmail.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] sched: Remove ARCH specific fpu_counter from task_struct
Date: Tue, 8 Oct 2013 10:02:12 +0200 [thread overview]
Message-ID: <20131008080212.GA6541@gmail.com> (raw)
In-Reply-To: <1381218389-16585-4-git-send-email-vgupta@synopsys.com>
* Vineet Gupta <Vineet.Gupta1@synopsys.com> wrote:
> From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
>
> fpu_counter in task_struct was used only by sh/x86.
> Both of these now carry it in ARCH specific thread_struct, hence this
> can now be removed from generic task_struct, shrinking it slightly for
> other arches.
>
> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-08 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 7:46 [PATCH v2 0/3] Move ARCH specific fpu_counter out of task_struct Vineet Gupta
2013-10-08 7:46 ` [PATCH v2 1/3] sh: Move fpu_counter into ARCH specific thread_struct Vineet Gupta
2013-10-08 7:46 ` Vineet Gupta
2013-10-08 7:46 ` [PATCH v2 3/3] sched: Remove ARCH specific fpu_counter from task_struct Vineet Gupta
2013-10-08 7:46 ` Vineet Gupta
2013-10-08 8:02 ` Ingo Molnar [this message]
2013-10-08 8:02 ` Ingo Molnar
2013-10-08 20:14 ` [PATCH v2 0/3] Move ARCH specific fpu_counter out of task_struct Andrew Morton
2013-10-09 5:55 ` Vineet Gupta
2013-10-09 5:39 ` [PATCH v2 2/3] x86: Move fpu_counter into ARCH specific thread_struct Vineet Gupta
2013-10-10 13:02 ` [PATCH v2 0/3] Move ARCH specific fpu_counter out of task_struct Vineet Gupta
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=20131008080212.GA6541@gmail.com \
--to=mingo@kernel.org \
--cc=Vineet.Gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.mundt@gmail.com \
--cc=peterz@infradead.org \
/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).