From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 1/4] nvme: move driver into subdirectory
Date: Mon, 28 Sep 2015 10:26:29 -0700 [thread overview]
Message-ID: <20150928172629.GA26554@infradead.org> (raw)
In-Reply-To: <14D8B1FAF8567C4FBE58AB68AB695A9D9B8498D7@ORSMSX115.amr.corp.intel.com>
Hi Phil,
On Mon, Sep 28, 2015@04:06:13PM +0000, Cayton, Phil wrote:
> Two questions:
> 1. Since this is the block driver for NVMe why would we not put this under block (e.g., drivers/block/nvme)
Because we mostly use that for simple block drivers. Everything that
is growing into a complex subsystems moves out, e.g. drivers/scsi,
drivers/cdrom/, drivers/memstick, drivers/mmc, etc.
> 2. Are we assuming any target code will go in this path as well? Why would not any target code go under drivers/target?
drivers/target is a SCSI target and a totally different codebase. In
retrospective it really should have been drivers/scsi/target.
next prev parent reply other threads:[~2015-09-28 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 1:35 [PATCH 1/4] nvme: move driver into subdirectory J Freyensee
2015-09-27 6:41 ` Christoph Hellwig
2015-09-27 7:14 ` Sagi Grimberg
2015-09-28 15:58 ` J Freyensee
2015-09-28 16:06 ` Cayton, Phil
2015-09-28 17:26 ` Christoph Hellwig [this message]
2015-09-27 7:11 ` Sagi Grimberg
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=20150928172629.GA26554@infradead.org \
--to=hch@infradead.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