From: 'Christoph Hellwig' <hch@infradead.org>
To: "Smart, James" <James.Smart@Emulex.Com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] dead code and missing statics in lpfc
Date: Wed, 9 Jun 2004 09:55:44 +0100 [thread overview]
Message-ID: <20040609085544.GB17870@infradead.org> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF28034F9464@xbl.ma.emulex.com>
On Tue, Jun 08, 2004 at 10:45:14AM -0400, Smart, James wrote:
> Christoph,
>
> We had not completed the effort relative to the comments. Sorry you thought
> your patch was ignored. They (including the prior one) was not.
>
> I believe that this week we will have completely dealt with the statics and
> symbols. One caveat though.. we have a lot of diagnostic and test tools that
> like to do low level error injection, testing, and data sampling. Our
> automated test suites are built heavily on this infrastructure. The way we
> are approaching these tools is as a separate kernel module. Therefore, the
> tools use quite a few of the "dead" symbols/functions. One of our jobs is to
> ensure that, where we sliced the interface between the driver and the tool
> module, that we did so appropriately, dead code in the driver should
> actually be in the tool module, and that we are exporting the minimum number
> of symbols. I am pushing to have this completed for the next drop as well,
> so we can put these comments to rest.
In either case exported symbols in the driver and dead symbols are completely
uninteresting for a kernel submission, so make sure you get rid of them
before you try to submit the driver.
next prev parent reply other threads:[~2004-06-09 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 14:45 [PATCH] dead code and missing statics in lpfc Smart, James
2004-06-09 8:55 ` 'Christoph Hellwig' [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 14:33 Smart, James
2004-06-10 14:43 ` Arjan van de Ven
2004-06-10 13:24 Smart, James
2004-06-10 13:36 ` Arjan van de Ven
2004-06-09 11:08 Smart, James
2004-06-10 11:17 ` 'Christoph Hellwig'
2004-05-31 10:04 Christoph Hellwig
2004-06-06 8:47 ` 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=20040609085544.GB17870@infradead.org \
--to=hch@infradead.org \
--cc=James.Smart@Emulex.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