Messages in this thread | | | Date | Sun, 11 Mar 2007 13:51:34 -0700 (PDT) | Subject | Re: [PATCH] MPT FUSION: Delete unused header files. | From | David Miller <> |
| |
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |