From: Andrew Morton <akpm@osdl.org>
To: Jeffrey Phillips Freeman <jeffreyfreeman@syncleus.com>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org,
ken@krwtech.com
Subject: Re: [patch 30/31] scsi: clean up warnings in Advansys driver
Date: Fri, 9 Jun 2006 00:04:29 -0700 [thread overview]
Message-ID: <20060609000429.51cf4e46.akpm@osdl.org> (raw)
In-Reply-To: <44891AF5.30406@syncleus.com>
On Fri, 09 Jun 2006 02:53:41 -0400
Jeffrey Phillips Freeman <jeffreyfreeman@syncleus.com> wrote:
> Oh, its great to see my name on the advansys list as a tester. You
> almost got filed away with the rest of my spam. I would love to test
> this patch but before i do is there some howto or overview document to
> help familarize me as a tester. I am comfortable with linuc and the
> kernel as well as patching. But i wasnt sure if there was a perticular
> version of the kernal i should try this patch on or a procedure i should
> follow. Any information that can be provided to go about this properly
> would be apprecaited. I would love to contribute, and if im going to
> contribute it should be done right!
Thanks.
Nothing fancy is needed - it would be sufficient to use the most recentl
major release (2.6.15, 2.6.16, 2.6.17, etc) in your daily operations and
report any problems.
I made a note of this in the changelog because with some of these drivers
nobody has the hardware - if someone decided to do some maintenance work on
this driver it could be useful for them to ask you to regression test their
changes. They'd ask something like "please install 2.6.18-rc2 and let us
know if it breaks".
prev parent reply other threads:[~2006-06-09 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 5:24 [patch 30/31] scsi: clean up warnings in Advansys driver akpm
2006-06-09 6:53 ` Jeffrey Phillips Freeman
2006-06-09 7:04 ` Andrew Morton [this message]
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=20060609000429.51cf4e46.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=James.Bottomley@steeleye.com \
--cc=jeffreyfreeman@syncleus.com \
--cc=ken@krwtech.com \
--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