public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: mingo@kernel.org, linux-kernel@vger.kernel.org
Cc: will.deacon@arm.com, linux@arm.linux.org.uk, ralf@linux-mips.org,
	egtvedt@samfundet.no, michael@amarulasolutions.com,
	cmetcalf@ezchip.com, peterz@infradead.org
Subject: [RFC][PATCH 0/7] sched: Remove finish_arch_switch()
Date: Wed, 29 Jul 2015 21:08:48 +0200	[thread overview]
Message-ID: <20150729190848.678796654@infradead.org> (raw)

Hi,

There were only a few architectures utilizing finish_arch_switch() and it looks
like they can all do without.

This means we can remove finish_arch_switch(); partly to make up for
introducing finish_arch_post_lock_switch(), partly to reduce the number of arch
hooks to consider.

Much thanks to Ralf, Will and Chris for helping out with this!


             reply	other threads:[~2015-07-29 19:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 19:08 Peter Zijlstra [this message]
2015-07-29 19:08 ` [RFC][PATCH 1/7] arm: Remove finish_arch_switch Peter Zijlstra
2015-08-04  7:39   ` Ingo Molnar
2015-08-04  8:26     ` Russell King - ARM Linux
2015-08-04  8:32       ` Will Deacon
2015-07-29 19:08 ` [RFC][PATCH 2/7] MIPS: Get rid of finish_arch_switch() Peter Zijlstra
2015-07-29 19:08 ` [RFC][PATCH 3/7] avr32: Remove finish_arch_switch() Peter Zijlstra
2015-07-30  5:40   ` Hans-Christian Egtvedt
2015-07-29 19:08 ` [RFC][PATCH 4/7] score: " Peter Zijlstra
2015-07-29 19:08 ` [RFC][PATCH 5/7] sh: Fold finish_arch_switch() into switch_to() Peter Zijlstra
2015-07-29 19:08 ` [RFC][PATCH 6/7] Remove finish_arch_switch Peter Zijlstra
2015-07-29 19:08 ` [RFC][PATCH 7/7] sched: Remove finish_arch_switch() Peter Zijlstra
2015-07-30  9:50 ` [RFC][PATCH 0/7] " Peter Zijlstra
2015-07-31  8:51   ` Ingo Molnar

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=20150729190848.678796654@infradead.org \
    --to=peterz@infradead.org \
    --cc=cmetcalf@ezchip.com \
    --cc=egtvedt@samfundet.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=michael@amarulasolutions.com \
    --cc=mingo@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=will.deacon@arm.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