From: "Stephen Bates" <sbates@raithlin.com>
To: "Jens Axboe" <axboe@fb.com>
Cc: sagi@grimberg.me, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
james_p_freyensee@linux.intel.com, jonathan.derrick@intel.com
Subject: Re: [PATCH 0/2] nvme: Improvements in sysfs entry for NVMe CMBs
Date: Fri, 16 Dec 2016 13:37:46 -0600 [thread overview]
Message-ID: <b2755703b7823eb26f282218ef29362b.squirrel@webmail.raithlin.com> (raw)
In-Reply-To: <365e0b2b-06b1-dc0b-a9ae-dc901ca98d6a@fb.com>
>> Jens I based this off v4.9 because for some reason your for-4.10/block
>> is missing my original CMB commit (202021c1a63c6)?
>
> for-4.10/block was forked off v4.9-rc1, and that patch didn't make it in
> until v4.9-rc2. Since for-4.10/block has been merged, any patches for this
> series or next should be based on my for-linus, or just master.
>
> Assuming these two apply directly to master as well?
>
>
Ah thanks for clearing up my confusion ;-). Yes, this series applies
cleanly to both your master and for-linus branches.
Stephen
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: "Stephen Bates" <sbates@raithlin.com>
To: "Jens Axboe" <axboe@fb.com>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, james_p_freyensee@linux.intel.com,
sagi@grimberg.me, jonathan.derrick@intel.com
Subject: Re: [PATCH 0/2] nvme: Improvements in sysfs entry for NVMe CMBs
Date: Fri, 16 Dec 2016 13:37:46 -0600 [thread overview]
Message-ID: <b2755703b7823eb26f282218ef29362b.squirrel@webmail.raithlin.com> (raw)
In-Reply-To: <365e0b2b-06b1-dc0b-a9ae-dc901ca98d6a@fb.com>
>> Jens I based this off v4.9 because for some reason your for-4.10/block
>> is missing my original CMB commit (202021c1a63c6)?
>
> for-4.10/block was forked off v4.9-rc1, and that patch didn't make it in
> until v4.9-rc2. Since for-4.10/block has been merged, any patches for this
> series or next should be based on my for-linus, or just master.
>
> Assuming these two apply directly to master as well?
>
>
Ah thanks for clearing up my confusion ;-). Yes, this series applies
cleanly to both your master and for-linus branches.
Stephen
WARNING: multiple messages have this Message-ID (diff)
From: sbates@raithlin.com (Stephen Bates)
Subject: [PATCH 0/2] nvme: Improvements in sysfs entry for NVMe CMBs
Date: Fri, 16 Dec 2016 13:37:46 -0600 [thread overview]
Message-ID: <b2755703b7823eb26f282218ef29362b.squirrel@webmail.raithlin.com> (raw)
In-Reply-To: <365e0b2b-06b1-dc0b-a9ae-dc901ca98d6a@fb.com>
>> Jens I based this off v4.9 because for some reason your for-4.10/block
>> is missing my original CMB commit (202021c1a63c6)?
>
> for-4.10/block was forked off v4.9-rc1, and that patch didn't make it in
> until v4.9-rc2. Since for-4.10/block has been merged, any patches for this
> series or next should be based on my for-linus, or just master.
>
> Assuming these two apply directly to master as well?
>
>
Ah thanks for clearing up my confusion ;-). Yes, this series applies
cleanly to both your master and for-linus branches.
Stephen
next prev parent reply other threads:[~2016-12-16 19:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 18:54 [PATCH 0/2] nvme: Improvements in sysfs entry for NVMe CMBs Stephen Bates
2016-12-16 18:54 ` [PATCH 1/2] nvme : Use correct scnprintf in cmb show Stephen Bates
2016-12-19 15:20 ` Jon Derrick
2016-12-19 15:20 ` Jon Derrick
2016-12-16 18:54 ` [PATCH 2/2] nvme: improve cmb sysfs reporting Stephen Bates
2016-12-16 18:54 ` Stephen Bates
2016-12-16 18:54 ` Stephen Bates
2016-12-19 15:42 ` Jon Derrick
2016-12-19 15:42 ` Jon Derrick
2017-01-09 19:37 ` Stephen Bates
2017-01-09 19:37 ` Stephen Bates
2016-12-16 19:23 ` [PATCH 0/2] nvme: Improvements in sysfs entry for NVMe CMBs Jens Axboe
2016-12-16 19:23 ` Jens Axboe
2016-12-16 19:37 ` Stephen Bates [this message]
2016-12-16 19:37 ` Stephen Bates
2016-12-16 19:37 ` Stephen Bates
2016-12-19 15:36 ` Jens Axboe
2016-12-19 15:36 ` Jens Axboe
2016-12-19 15:36 ` Jens Axboe
2017-01-09 19:35 ` Stephen Bates
2017-01-09 19:35 ` Stephen Bates
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=b2755703b7823eb26f282218ef29362b.squirrel@webmail.raithlin.com \
--to=sbates@raithlin.com \
--cc=axboe@fb.com \
--cc=james_p_freyensee@linux.intel.com \
--cc=jonathan.derrick@intel.com \
--cc=linux-block@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.