From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] aic7* claims all checked EISA io ranges
Date: Tue, 08 Apr 2003 17:12:39 -0600 [thread overview]
Message-ID: <3688420000.1049843559@aslan.btc.adaptec.com> (raw)
In-Reply-To: <1049843229.2107.46.camel@mulgrave>
> I take it 2.5 is up to date, right? Because otherwise we should have
> seen an update notice go across linux-scsi@vger.kernel.org.
In the past, I have sent mail directly to Linus which has worked for 2.5.
Unfortunately, it looks like he has not applied the last bundle I posted
to him on 2003/03/25. This is the same bk output as posted on my website.
> This problem looks to be present in 2.5, so should I apply the patch?
It would be better to just upgrade the driver with bits I submitted to
Linus. I have another update coming to correctly fix the del_timer_sync()
issue since the last, unsanctioned, change in this area has a large potential
to cause a deadlock.
--
Justin
next prev parent reply other threads:[~2003-04-08 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 23:07 [PATCH] aic7* claims all checked EISA io ranges James Bottomley
2003-04-08 23:12 ` Justin T. Gibbs [this message]
2003-04-08 23:28 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 1:21 [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u Chuck Ebbert
2003-04-09 11:13 ` Alan Cox
2003-04-09 17:34 ` Justin T. Gibbs
2003-04-10 11:20 ` [PATCH] aic7* claims all checked EISA io ranges Stephan von Krawczynski
2003-04-10 16:44 ` Justin T. Gibbs
2003-04-11 8:51 ` Stephan von Krawczynski
2003-04-11 11:39 ` Stephan von Krawczynski
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=3688420000.1049843559@aslan.btc.adaptec.com \
--to=gibbs@scsiguy.com \
--cc=James.Bottomley@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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.