Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: peter fuerst <post@pfrst.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] IP28 support
Date: Thu, 29 Nov 2007 11:01:01 +0100	[thread overview]
Message-ID: <20071129100101.GB9106@alpha.franken.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0711280206450.407@Indigo2.Peter>

On Wed, Nov 28, 2007 at 02:33:37AM +0100, peter fuerst wrote:
> unfortunately a little change to ip28_be_interrupt is needed (sorry, that
> it was not yet applied):

no problem, I've integrated it in the updated IP28 patch. I also
killed the second check for gio_err_stat a few line below, because
isn't usefull any longer.

Thoms.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2007-11-29 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 22:40 [PATCH] IP28 support Thomas Bogendoerfer
2007-11-28  1:33 ` peter fuerst
2007-11-29 10:01   ` Thomas Bogendoerfer [this message]
2007-11-28 14:34 ` Ralf Baechle
2007-11-29  9:58   ` Thomas Bogendoerfer
2007-11-29 12:15     ` Ralf Baechle

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=20071129100101.GB9106@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-mips@linux-mips.org \
    --cc=post@pfrst.de \
    /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