From: David Miller <davem@davemloft.net>
To: eric.moore@lsi.com
Cc: rpjday@mindspring.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] MPT FUSION: Delete unused header files.
Date: Sun, 11 Mar 2007 13:51:34 -0700 (PDT) [thread overview]
Message-ID: <20070311.135134.125894940.davem@davemloft.net> (raw)
In-Reply-To: <20070311195553.GA12056@lsil.com>
From: Eric Moore <eric.moore@lsi.com>
Date: Sun, 11 Mar 2007 13:55:54 -0600
> On Sat, Mar 10, 2007 at 04:57:35PM -0500, Robert P. J. Day wrote:
> >
> > Delete apparently unused header files.
> >
> > Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
> >
> > ---
> >
> > drivers/message/fusion/lsi/mpi_inb.h | 221 ----------------------
> > drivers/message/fusion/lsi/mpi_log_fc.h | 89 --------
> > 2 files changed, 310 deletions(-)
> >
>
> NACK.
>
> Thanks, but no thanks. Don't remove these header files. These are the mpi
> header files that define the interface between firmware and drivers. This
> set of headers are bundled with each flavor OS, and we are constantly
> providing update files when changes occur.
>
> With respect to mpi_log_fc.h - this defines the loginfo for fibre channel
> protocal. This is a easy lookup to for LSI Logic customers to better
> understand the kind of errors returned from firmware, and help reduce number
> of support generated request, as the end user can merely lookup the unqiue
> id in the header file. mpi_inb.h, is header for fibre channel protocal
> definii
> ng the inband-management interface, and maybe implemented some day.
This is not the criteria for keeping source files in the tree,
they really have to be used to stay there.
If you want to document the error codes and other interfaces, publish
the programming manual for your hardware on a web site.
Sorry if you don't like this, but the linux kernel is about more than
your driver and your needs, it's about the needs of maintaining a huge
behemoth source tree in some sane manner and part of achieving that
goal is important tasks such as eliminating unused code and source
files.
next prev parent reply other threads:[~2007-03-11 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 21:57 Robert P. J. Day
2007-03-11 19:55 ` Eric Moore
2007-03-11 20:51 ` David Miller [this message]
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
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=20070311.135134.125894940.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=eric.moore@lsi.com \
--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
all inboxes | Powered by JetHome®