public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-scsi@vger.kernel.org
Subject: Re: Move scsi.h, hosts.h to include/linux/scsi ?
Date: Mon, 17 Feb 2003 14:07:56 +0100	[thread overview]
Message-ID: <20030217130756.GA3510@mars.ravnborg.org> (raw)
In-Reply-To: <20030217125821.A25189@infradead.org>

On Mon, Feb 17, 2003 at 12:58:21PM +0000, Christoph Hellwig wrote:
> > In general just combining all the stuff in a single scsi.h file
> > (the other alternative)  looks ugly to me.
> 
> Why?  If you think the current hosts.h make sense please explain
> me the rules on why stuff is in hosts.h instead of scsi.h..

It was just my first hand impressions that hosts.c had something to do
upper.h.
I have not looked into scsi before - and I'm not planning to that
except on a janitorial level. In other words I can do simple stuff
that moves definitions around, but I do not claim I understand the
SCSI subsystem. And I do not plan to invest the time needed to
understand it.
Hope that clarifies.

As I wrote in the previous mail, I'm not going to do any split-up as
you suggested. Simply because it would take much more time
understanding the SCSI subsystem than actually doing the split-up.

My only incentive is to avoid those ugly includes that requires an
extra option to gcc in my current kbuild patch for separate objdir.

	Sam

  reply	other threads:[~2003-02-17 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-16 21:14 Move scsi.h, hosts.h to include/linux/scsi ? Sam Ravnborg
2003-02-17 12:18 ` Christoph Hellwig
2003-02-17 12:53   ` Sam Ravnborg
2003-02-17 12:58     ` Christoph Hellwig
2003-02-17 13:07       ` Sam Ravnborg [this message]
2003-02-17 14:18         ` 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=20030217130756.GA3510@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=hch@infradead.org \
    --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