All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schiele <rschiele@uni-mannheim.de>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.uni-mannheim.de: Returned mail: see transcript for details])
Date: Tue, 8 Apr 2003 22:51:36 +0200	[thread overview]
Message-ID: <20030408205136.GA8144@schiele.local> (raw)
In-Reply-To: <3566580000.1049834178@aslan.btc.adaptec.com>

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

On Tue, Apr 08, 2003 at 02:36:19PM -0600, Justin T. Gibbs wrote:
> > Hello.
> > 
> > Some days ago a bug was introduced in aic7xxx by applying the aic7xxx driver
> > upgrade to both the 2.4 and the 2.5 tree.
> 
> This particular defect was corrected in all versions of the aic7xxx
> driver released by me after March 9th.  See the driver CHANGELOG in
> the driver source distribution for details.
> 
> http://people.FreeBSD.org/~gibbs/linux/SRC/

Thanks for your note.  Hope you didn't feel offended.  At least this was not
my intention.  I just wanted to notify all people related to the affected
driver.

So it's up to the kernel tree maintainers to bring this fix into their trees.

Robert

-- 
Robert Schiele			Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker	mailto:rschiele@uni-mannheim.de

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

  reply	other threads:[~2003-04-08 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08  7:18 [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.uni-mannheim.de: Returned mail: see transcript for details]) Robert Schiele
2003-04-08 20:36 ` Justin T. Gibbs
2003-04-08 20:51   ` Robert Schiele [this message]
2003-04-08 20:18     ` Alan Cox
2003-04-08 21:32       ` Justin T. Gibbs
2003-04-09  6:01       ` Robert Schiele

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=20030408205136.GA8144@schiele.local \
    --to=rschiele@uni-mannheim.de \
    --cc=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.