From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: 4 Patch summary of PCIe re-arrangement of nvme code for future technology expansion
Date: Sat, 26 Sep 2015 18:34:19 -0700 [thread overview]
Message-ID: <1443317659.4357.22.camel@linux.intel.com> (raw)
The four patch series following this email is based on a previous email
thread and the following suggestion:
a) move files to a new directory.
b) start splitting struct nvme_dev into a generic struct nvme_ctrl
and a PCI-specific nvme_pci_ctrl
The goal is still based on the previous patch submission (subject "Move
nvme driver source into subdirectory and move pci specifics from core
into separate file") which:
- moved files to a new directory
- split data structures
- split files
- introduced a new internal API
to enable future technology expansion of the NVMe protocol.
reply other threads:[~2015-09-27 1:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1443317659.4357.22.camel@linux.intel.com \
--to=james_p_freyensee@linux.intel.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;
as well as URLs for NNTP newsgroup(s).