Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@linux-mips.org
Subject: Re: SMTC Patch
Date: Thu, 31 May 2007 17:13:04 +0100	[thread overview]
Message-ID: <20070531161304.GD4425@linux-mips.org> (raw)
In-Reply-To: <465C2DD8.6090208@mips.com>

On Tue, May 29, 2007 at 03:42:48PM +0200, Kevin D. Kissell wrote:

> The attached patch fixes some problems with the linux-mips.org
> 2.6.21 kernel for SMTC kernels for the Malta platform.
> 
> The fix to smtc.c just eliminates a warning that crept in.
> 
> The fixes to traps.c eliminate a hypothetical problem with
> out-of-bounds arguments (which were being reported, but acted
> upon anyway, which was somewhat insane)

set_vi_srs_handler is a void function, so currently can't return an
error either and not scribbling around isn't really a solution either
because no matter waht, for a vector number >= 8 won't work right.
So I went for a more drastic solution using BUG_ON().

> and a real one with
> PageMask going uninitialized in VPE 1 on any MIPS MT processor
> that doesn't reset PageMask to a sane value, which the archtecture
> does not require.
> 
> The restoration of the #define in mips-boards/generic/time.c
> is necessary to make the Malta SMTC kernel build.  If whoever
> deleted it has a good reason for it not to be done the way it's
> done, that's OK, but *some* definition must be provided.

I really don't see why we should fix code that writes r/o bits in a
failed attempt to do something that already happens elsewhere, so I
applied the patch which Chris sent in private.

Btw, your patch was dealing with four separate issues.  Would be kind of
handy if something like that would be submitted as four separate patches.

  Ralf

PS: A Signed-off-by: line please!

      reply	other threads:[~2007-05-31 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 13:42 SMTC Patch Kevin D. Kissell
2007-05-31 16:13 ` Ralf Baechle [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=20070531161304.GD4425@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.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