From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Peter Missel <peter.missel@onlinehome.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: SYM8xx_2 driver ignores certain EEPROM settings
Date: Fri, 31 Dec 2004 09:01:35 -0600 [thread overview]
Message-ID: <1104505295.5247.2.camel@mulgrave> (raw)
In-Reply-To: <20041231145306.GB18080@parcelfarce.linux.theplanet.co.uk>
On Fri, 2004-12-31 at 14:53 +0000, Matthew Wilcox wrote:
> I don't need you to do that -- I know the ability has been removed from the
> driver. I bet I can put it back without disturbing things too much.
There are two ways of doing this:
1) one would be to have the hard coded limits in the sym2 driver (like
they were previously) and make sure we don't allow setting or
negotiating over them or
2) have the limits stored in the SPI transport class and make it enforce
them.
1) Is probably easier (less code since you just put back a modification
of what was taken out) 2) would be more globally useful, though ...
James
next prev parent reply other threads:[~2004-12-31 15:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200412311343.42484.peter.missel@onlinehome.de>
2004-12-31 14:53 ` SYM8xx_2 driver ignores certain EEPROM settings Matthew Wilcox
2004-12-31 15:01 ` James Bottomley [this message]
2004-12-31 15:20 ` Peter Missel
2005-01-01 22:16 ` Matthias Andree
2005-01-02 0:28 ` Peter Missel
2005-01-02 0:40 ` Matthias Andree
2005-01-02 1:03 ` Matthew Wilcox
2005-01-02 9:58 ` Peter Missel
2005-02-26 19:34 ` Peter Missel
2005-04-08 22:57 ` Peter Missel
2005-04-09 14:02 ` Matthew Wilcox
2005-04-09 21:44 ` Peter Missel
2005-04-18 17:55 ` Peter Missel
2005-05-04 21:47 ` SYM8xx_2 sync speed negotiation Peter Missel
2005-06-18 21:52 ` Peter Missel
2005-06-19 10:45 ` endless loop problem with SYM8xx_2: unexpected disconnect Christian Werner
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=1104505295.5247.2.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=peter.missel@onlinehome.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