From: Keith Busch <keith.busch@intel.com>
To: Jens Axboe <axboe@fb.com>
Cc: Scott Bauer <scott.bauer@intel.com>,
linux-block@vger.kernel.org,
Rafael Antognolli <rafael.antognolli@intel.com>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Jon Derrick <jonathan.derrick@intel.com>
Subject: Re: [PATCHv4 4/4] block/sed: Embed function data into the function sequence
Date: Wed, 22 Feb 2017 12:22:39 -0500 [thread overview]
Message-ID: <20170222172238.GA28937@localhost.localdomain> (raw)
In-Reply-To: <51275275-9cff-ce94-f760-3572161dde79@fb.com>
On Wed, Feb 22, 2017 at 09:47:53AM -0700, Jens Axboe wrote:
> I see, I found it now. Guys, let's get this process streamlined a bit
> more. This whole thing has been a flurry of patches and patchseries,
> posted by either you or Jon. Previous patch series was 1-4 patches
> posted by you, and then patch #4 is replaced by a single patch from Jon,
> posted outside of that thread. Honestly, I feel like this should have
> been pushed to 4.12 instead, it clearly wasn't ready before the merge
> window.
Sorry, I'll run interference to help ensure future patch series are
complete and coherent in one thread.
next prev parent reply other threads:[~2017-02-22 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:59 [PATCHv4 0/4] OPAL patches, cont'd Jon Derrick
2017-02-21 18:59 ` [PATCHv4 4/4] block/sed: Embed function data into the function sequence Jon Derrick
2017-02-21 23:03 ` Scott Bauer
2017-02-22 7:13 ` Christoph Hellwig
2017-02-22 14:35 ` Jon Derrick
2017-02-22 16:10 ` Jens Axboe
2017-02-22 16:13 ` Scott Bauer
2017-02-22 16:47 ` Jens Axboe
2017-02-22 17:22 ` Keith Busch [this message]
2017-02-22 2:42 ` [PATCHv4 0/4] OPAL patches, cont'd Jens Axboe
2017-02-22 3:14 ` Scott Bauer
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=20170222172238.GA28937@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jonathan.derrick@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=rafael.antognolli@intel.com \
--cc=scott.bauer@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