From: J Freyensee <james_p_freyensee@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Sagi Grimberg <sagi@grimberg.me>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
Jens Axboe <axboe@fb.com>
Subject: Re: [PATCH] nvme-loop: add configfs dependency
Date: Mon, 11 Jul 2016 09:12:17 -0700 [thread overview]
Message-ID: <1468253537.9164.52.camel@linux.intel.com> (raw)
In-Reply-To: <20160710121417.GA21551@lst.de>
On Sun, 2016-07-10 at 14:14 +0200, Christoph Hellwig wrote:
> On Thu, Jul 07, 2016 at 08:35:17AM -0600, Jens Axboe wrote:
> > Thanks Arnd, applied.
>
> Actually I think we should replace the select with the depends. In
> fact I though I had done that a while ago, but I must have messed it
> up.
>
> Btw - do you plan to grab patches directly from the list now or
> do you want me to queue them up? There are a few more pending on
> the list that should go in:
>
> http://lists.infradead.org/pipermail/linux-nvme/2016-June/005150.html
> (whole series)
>
> http://lists.infradead.org/pipermail/linux-nvme/2016-July/005290.html
> (needs the attribution fixed to be from Ming)
I can re-send the patch changing "Fix by: " to "From: " if that helps.
Jay
next prev parent reply other threads:[~2016-07-11 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 9:01 [PATCH] nvme-loop: add configfs dependency Arnd Bergmann
2016-07-07 14:35 ` Jens Axboe
2016-07-10 12:14 ` Christoph Hellwig
2016-07-11 16:12 ` J Freyensee [this message]
2016-07-11 20:29 ` Arnd Bergmann
2016-07-12 15:36 ` Jens Axboe
2016-07-12 15:38 ` Jens Axboe
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=1468253537.9164.52.camel@linux.intel.com \
--to=james_p_freyensee@linux.intel.com \
--cc=arnd@arndb.de \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).