public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Brad Boyer <flar@cynthia.pants.nu>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k/mac: Allocate IOP message pool and queues dynamically
Date: Mon, 1 Jul 2013 14:59:32 -0700	[thread overview]
Message-ID: <20130701215932.GA12663@cynthia.pants.nu> (raw)
In-Reply-To: <alpine.LNX.2.00.1307011325520.9968@nippy.intranet>

On Mon, Jul 01, 2013 at 05:46:48PM +1000, Finn Thain wrote:
> 
> On Sun, 30 Jun 2013, Geert Uytterhoeven wrote:
> 
> > -
> > -/*
> > - * Register the interrupt handler for the IOPs.
> > - * TODO: might be wrong for non-OSS machines. Anyone?
> > - */
> > -
> > -void __init iop_register_interrupts(void)
> > -{
> > -	if (iop_ism_present) {
> > +		/*
> > +		 * Register the interrupt handler for the IOPs.
> > +		 * TODO: might be wrong for non-OSS machines. Anyone?
> 
> My testing with a non-OSS machine (Quadra 950) indicates that the TODO is 
> obsolete. And the comment "register the interrupt handler for the IOPs" is 
> a bit silly. It merely re-phrases the code. Otherwise, this patch looks 
> good to me. Thanks.

The code was all originally written and tested only on the IIfx. That's
all JMT had, and at the time it was all I had as well. I have since
acquired a Quadra 950. Lots of these comments are just out of date. I
know it got tested on either a Quadra 900 or Quadra 950 after that
comment was put in the source.

	Brad Boyer
	flar@allandria.com

      reply	other threads:[~2013-07-01 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 10:02 [PATCH] m68k/mac: Allocate IOP message pool and queues dynamically Geert Uytterhoeven
2013-07-01  6:52 ` Brad Boyer
2013-07-01  7:48   ` Finn Thain
2013-07-01 22:48     ` Brad Boyer
2013-07-01  7:46 ` Finn Thain
2013-07-01 21:59   ` Brad Boyer [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=20130701215932.GA12663@cynthia.pants.nu \
    --to=flar@cynthia.pants.nu \
    --cc=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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