public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Michael Schmitz <schmitzmic@gmail.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] g_NCR5380: Bug fix and some enhancements
Date: Thu, 8 Dec 2016 19:45:02 +0100	[thread overview]
Message-ID: <201612081945.02906.linux@rainbow-software.org> (raw)
In-Reply-To: <cover.1480917789.git.fthain@telegraphics.com.au>

On Monday 05 December 2016 07:07:19 Finn Thain wrote:
> This patch series is based on the one submitted recently by Ondrej Zary.
>
> This version has a different irq probing fix for HP C2502 boards and
> a more comprehensive patch to change the default irq parameter.
>
> It needs testing on actual ISA hardware.

Tested on HP C2502 (53C400A chip), Canon FG2-5202 (53C400 chip), DTC-3181L 
(DTCT-436P chip) and MS-PNR (53C400A chip) ISA cards - everything works fine!

Thanks.

Tested-by: Ondrej Zary <linux@rainbow-software.org>

BTW. The release-region fix (my previous patch 6/6) has disappeared somehow. 
Should I resubmit?

-- 
Ondrej Zary

  parent reply	other threads:[~2016-12-08 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05  6:07 [PATCH 0/4] g_NCR5380: Bug fix and some enhancements Finn Thain
2016-12-05  6:07 ` [PATCH 1/4] g_NCR5380: Check for chip presence before calling NCR5380_init() Finn Thain
2016-12-05  6:07 ` [PATCH 4/4] g_NCR5380: Autoprobe board IRQ by default Finn Thain
2016-12-05  6:07 ` [PATCH 3/4] g_NCR5380: Fix automatic IRQ on HP C2502 cards Finn Thain
2016-12-05  6:07 ` [PATCH 2/4] g_NCR5380: Use probe_irq_*() for IRQ probing Finn Thain
2016-12-08 18:45 ` Ondrej Zary [this message]
2016-12-08 22:27   ` [PATCH 0/4] g_NCR5380: Bug fix and some enhancements Finn Thain
2016-12-08 21:59 ` Martin K. Petersen

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=201612081945.02906.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=fthain@telegraphics.com.au \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=schmitzmic@gmail.com \
    /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