From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Alexey Dobriyan <adobriyan@openvz.org>
Cc: akpm@osdl.org, dev@sw.ru, linux-kernel@vger.kernel.org,
devel@openvz.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/2] Consolidate bust_spinlocks()
Date: Thu, 18 Jan 2007 12:39:25 +0100 [thread overview]
Message-ID: <1169120365.5621.4.camel@localhost> (raw)
In-Reply-To: <20070118111626.GA6040@localhost.sw.ru>
On Thu, 2007-01-18 at 14:16 +0300, Alexey Dobriyan wrote:
> From: Kirill Korotaev <dev@sw.ru>
>
> Part of long forgotten patch
> http://groups.google.com/group/fa.linux.kernel/msg/e98e941ce1cf29f6?dmode=source
> Since then, m32r grabbed two copies.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@openvz.org>
> ---
>
> arch/i386/mm/fault.c | 26 --------------------------
> arch/ia64/kernel/traps.c | 30 ------------------------------
> arch/m32r/mm/fault-nommu.c | 26 --------------------------
> arch/m32r/mm/fault.c | 26 --------------------------
> arch/s390/mm/fault.c | 26 --------------------------
> arch/x86_64/mm/fault.c | 21 ---------------------
> lib/Makefile | 4 ++--
> lib/bust_spinlocks.c | 2 +-
> 8 files changed, 3 insertions(+), 158 deletions(-)
NACK for the s390 part. lib/bust_spinlocks.c does an unblank_screen if
CONFIG_VT is defined. That is not good enough for s390 because we do not
have CONFIG_VT nor unblank_screen but still require that console_unblank
is called.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2007-01-18 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 11:16 [PATCH 1/2] Consolidate bust_spinlocks() Alexey Dobriyan
2007-01-18 11:39 ` Martin Schwidefsky [this message]
2007-01-18 16:26 ` Alexey Dobriyan
2007-01-19 9:27 ` Martin Schwidefsky
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=1169120365.5621.4.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=adobriyan@openvz.org \
--cc=akpm@osdl.org \
--cc=dev@sw.ru \
--cc=devel@openvz.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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