public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@drugphish.ch>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: Valdis.Kletnieks@vt.edu,
	"Robert P. J. Day" <rpjday@mindspring.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] MPT FUSION: Delete unused header files.
Date: Mon, 12 Mar 2007 20:44:14 +0100	[thread overview]
Message-ID: <45F5AD8E.2080105@drugphish.ch> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D70623ED6@NAMAIL4.ad.lsil.com>

>> 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. 

Allow me to shortly chime in here:

I'm the author of the mpt-status user space tool (a simple alternative 
to your Java GUI tool), which queries LSI controllers and reports back 
the RAID status and the synchronization state; so I have waded through 
the driver source code quite a lot. My question:

> 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.    

I would really like to see "sanitized" kernel headers, so is it possible 
to have your headers inside ../drivers/message/fusion{,/lsi} somehow 
inserted into the process of the headers_install target?

Best regards,
Roberto Nibali, ratz
-- 
echo 
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc

  reply	other threads:[~2007-03-12 20:12 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 [this message]
2007-03-12 21:00       ` David Miller
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=45F5AD8E.2080105@drugphish.ch \
    --to=ratz@drugphish.ch \
    --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