From: David Miller <davem@davemloft.net>
To: Eric.Moore@lsi.com
Cc: Valdis.Kletnieks@vt.edu, rpjday@mindspring.com,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] MPT FUSION: Delete unused header files.
Date: Mon, 12 Mar 2007 14:00:25 -0700 (PDT) [thread overview]
Message-ID: <20070312.140025.21595408.davem@davemloft.net> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D70623ED6@NAMAIL4.ad.lsil.com>
From: "Moore, Eric" <Eric.Moore@lsi.com>
Date: Mon, 12 Mar 2007 10:19:18 -0600
> Valdis.Kletnieks silly little rant:
>
> > Certainly appropriate content for something on your website,
> > and vendors who
> > provide programs like dmidecode and parsemce are always
> > welcome. I could
> > probably be convinced that such info should have at least a
> > pointer somewhere
> > in Documentation/lsi_debug.txt or some such. But quite
> > frankly, if I'm reduced
> > to wading through *.h files to figure out what some
> > recalcitrant hardware is
> > upset about, there's been a failure in documentation.
> > *ESPECIALLY* if I
> > go look at drivers/whatever/source.c and it doesn't even
> > *reference* the *.h
> > file in question.
>
>
> Its apparent to me that you don't have our hardware, nor have you
> actually waded thru this driver source code.
>
> If you did, you would of noticed that the header you want to delete, is
> actually referenced in the *.c source code. The file "mpi_log_fc.h",
> is indeed mentioned in mptbase.c, in the function called
> mpt_fc_log_info, in the documention section above the function. This
> header file is very helpful to those supporting our hardware, and those
> using it
> For SAS(mpi_log_sas.h), I have broken out each loginfo in the strings
> you will find defined in originator_str, iop_code_str, pl_code_str, etc,
> I probably do that with fibre.
>
> If its that important to you to have the header files included, I will
> provide a patch that does that.
If you're going to include it just for the sake of including it, not
because the code in question actually uses types or function
declarations defined in there, don't bother, you're just using an
anti-social mechanism to keep this header file in the tree.
Please, let's kill this header file if it is unused.
next prev parent reply other threads:[~2007-03-12 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 21:57 [PATCH] MPT FUSION: Delete unused header files Robert P. J. Day
2007-03-11 19:55 ` Eric Moore
2007-03-11 20:51 ` David Miller
2007-03-11 21:11 ` Robert P. J. Day
2007-03-11 22:32 ` Valdis.Kletnieks
2007-03-12 16:19 ` Moore, Eric
2007-03-12 19:44 ` Roberto Nibali
2007-03-12 21:00 ` David Miller [this message]
2007-03-12 21:29 ` Moore, Eric
2007-03-12 21:31 ` David Miller
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=20070312.140025.21595408.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Eric.Moore@lsi.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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