From: Christoph Hellwig <hch@lst.de>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Christoph Hellwig <hch@lst.de>,
jejb@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aacraid: use kthread_ API
Date: Tue, 14 Feb 2006 18:54:59 +0100 [thread overview]
Message-ID: <20060214175459.GF19080@lst.de> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F0222C7CC@otce2k03.adaptec.com>
On Tue, Feb 14, 2006 at 12:53:06PM -0500, Salyzyn, Mark wrote:
> Looks good by me, save that it would be nicer to use either
> AAC_DRIVERNAME or aac->name instead of yet another hard coded string.
I just copied that from the previous code. But yes, avoiding the
hardcoded string would be nicer. I'll send a followup-patch ASAP.
next prev parent reply other threads:[~2006-02-14 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 17:53 [PATCH] aacraid: use kthread_ API Salyzyn, Mark
2006-02-14 17:54 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-14 17:45 Christoph Hellwig
2006-02-14 18:00 ` Christoph Hellwig
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=20060214175459.GF19080@lst.de \
--to=hch@lst.de \
--cc=jejb@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
/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).