mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Jim Nelson <james4765@cwazy.co.uk>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	linux-kernel@vger.kernel.org,
	linuxsh-shmedia-dev@lists.sourceforge.net
Subject: Re: [PATCH /3] sh64: remove cli()/sti() from arch/sh64/*
Date: Wed, 5 Jan 2005 19:28:50 +0200	[thread overview]
Message-ID: <20050105172850.GA21683@linux-sh.org> (raw)
In-Reply-To: <41DB5ADB.9060102@cwazy.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

On Tue, Jan 04, 2005 at 10:11:23PM -0500, Jim Nelson wrote:
> Everything I've looked at so far has been for single-processor systems 
> AFAICT - embedded processors, evaluation boards, etc.  I do not pretend 
> to have intimate familiarity with the hardware in question, and I will 
> be much more careful when I reach anything that can be plugged into an 
> SMP box, but I was grabbing the low-hanging fruit first.  The nasty 
> stuff (drivers/char, for example) will come later.
> 
> That's why I cc'd the arch maintainers - figured they'd whack me with a 
> cluebat if I'd overlooked something.

Yes, these are all UP cases, so at least for the sh and sh64 cases these
specific changes are fine.

sh ripped out the save_and_cli() mess a long time ago (during early 2.5
before Linus added the UP compat stuff), so these at least shouldn't
have been there in the first place (mpc1211 wasn't added until after the
fact however and seems to have gotten overlooked).

Anyways, I'll apply these patches to their respective trees, thanks.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-01-05 17:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05  2:22 James Nelson
2005-01-05  2:22 ` [PATCH /3] sh64: remove cli()/sti() in arch/sh64/kernel/time.c James Nelson
2005-01-05  2:34 ` [PATCH /3] sh64: remove cli()/sti() from arch/sh64/* Al Viro
2005-01-05  3:11   ` Jim Nelson
2005-01-05 17:28     ` Paul Mundt [this message]

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=20050105172850.GA21683@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=james4765@cwazy.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxsh-shmedia-dev@lists.sourceforge.net \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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

Powered by JetHome