From: Christoph Hellwig <hch@lst.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Christoph Hellwig <hch@lst.de>, linux-scsi@vger.kernel.org
Subject: Re: [RFTesters] Re: [PATCH] refactor tmscsim inititalization code
Date: Fri, 10 Sep 2004 15:32:54 +0200 [thread overview]
Message-ID: <20040910133254.GB32530@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.60.0409071040120.2966@poirot.grange>
On Tue, Sep 07, 2004 at 05:29:43PM +0200, Guennadi Liakhovetski wrote:
> Hi
>
> I've looked through the patch - I liked it! Still, I've got a few
> questions / remarks to this one.
>
> 1) My big problem with this patch is, that I don't have any AM53C7974
> based hardware with EEPROM, and you re-write the EEPROM handling
> functions. Although, it does look like you just inlined some of them and
> removed redundant code. Do you have the hardware to test it? If not - I
> guess, we'd have to ask for volunteers to test it. Your patch is a bit
> less than trivial:-) If nobody volunteers, well, I'll have to try to prove
> the equivalence myself:-)
I'll do a new patch with that part excluded (and ontop of all the
patches currently pending for tmscsim)
> 2) I just realised - we have 2 possibilities to pass parameters to
> tmscsim, if it is compiled into the kernel - with tmscsim.tmscsim=...
> and with tmscsim=... I guess, breaking scripts by removing one of them now
> wouldn't be good... But we could put a warning printk() in dc390_setup
> "Deprecated! Use tmscsim.tmscsim=... This will be removed real soon
> now!\n" should we?
I think we should deprecated both and use an easy to understand
module_param-based interface.
> 3) There's a typo:
>
> >+static void __devinit dc390_eeprom_prepare_read(struct pci_dev *pdev, u8
> >cd)
>
> should be
>
> >+static void __devinit dc390_eeprom_prepare_read(struct pci_dev *pdev, u8
> >cmd)
thanks.
> 4) Against which kernel version is it? It did apply to some my version,
> but with some fuzz / offsets.
I don't remember anymore, but I'll rediff anyway.
next prev parent reply other threads:[~2004-09-10 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 13:02 [PATCH] refactor tmscsim inititalization code Christoph Hellwig
2004-09-07 15:29 ` [RFTesters] " Guennadi Liakhovetski
2004-09-10 13:32 ` Christoph Hellwig [this message]
2004-09-17 19:05 ` Guennadi Liakhovetski
2004-09-20 15:24 ` Christoph Hellwig
2004-09-20 20:35 ` Guennadi Liakhovetski
2004-09-21 5:41 ` Guennadi Liakhovetski
2004-09-07 16:29 ` Guennadi Liakhovetski
2004-09-12 11:37 ` Christoph Hellwig
2004-09-17 19:49 ` Guennadi Liakhovetski
2004-09-18 20:43 ` Guennadi Liakhovetski
2004-09-14 19:05 ` Christoph Hellwig
[not found] <4153004D.6010107@yk.rim.or.jp>
[not found] ` <415302C7.9080809@yk.rim.or.jp>
[not found] ` <Pine.LNX.4.60.0409240035460.5028@poirot.grange>
[not found] ` <415357C3.9040509@yk.rim.or.jp>
[not found] ` <Pine.LNX.4.60.0409240716470.3682@poirot.grange>
[not found] ` <41545316.4080908@yk.rim.or.jp>
[not found] ` <41545BB5.1050609@yk.rim.or.jp>
[not found] ` <Pine.LNX.4.60.0409242146330.5286@poirot.grange>
[not found] ` <20040925131539.GB19231@lst.de>
[not found] ` <Pine.LNX.4.60.0409251848560.2258@poirot.grange>
[not found] ` <20040927151143.GA21345@lst.de>
2004-11-12 21:40 ` [RFTesters] " Guennadi Liakhovetski
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=20040910133254.GB32530@lst.de \
--to=hch@lst.de \
--cc=g.liakhovetski@gmx.de \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).