From: Richard Weinberger <richard@nod.at>
To: Bart Van Assche <bart.vanassche@sandisk.com>,
Dan Williams <dan.j.williams@intel.com>,
axboe@fb.com
Cc: linux-nvdimm@lists.01.org, Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
hch@lst.de
Subject: Re: [PATCH v5 3/5] um: track 'parent' device in a local variable
Date: Tue, 28 Jun 2016 10:14:07 +0200 [thread overview]
Message-ID: <577231CF.6000301@nod.at> (raw)
In-Reply-To: <5965be1f-6b0b-d6f7-f6b0-d73b9be87267@sandisk.com>
Am 28.06.2016 um 09:23 schrieb Bart Van Assche:
> On 06/27/2016 09:30 PM, Dan Williams wrote:
>> In preparation for the removal of 'driverfs_dev' from 'struct gendisk'
>> use a local variable to track the parented vs un-parented case in
>> ubd_disk_register().
>
> Reviewed-by: Bart Van Assche <bart.vanassche@sandisk.com>
Acked-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
next prev parent reply other threads:[~2016-06-28 8:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <146705579255.39775.12551436695635245858.stgit@dwillia2-desk3.amr.corp.intel.com>
2016-06-27 19:29 ` [PATCH v5 1/5] block: introduce device_add_disk() Dan Williams
2016-06-27 19:30 ` [PATCH v5 2/5] mmc: move 'parent' tracking to mmc_blk_data Dan Williams
2016-06-28 7:26 ` Bart Van Assche
2016-06-28 11:57 ` Christoph Hellwig
2016-07-12 13:51 ` Ulf Hansson
2016-06-27 19:30 ` [PATCH v5 3/5] um: track 'parent' device in a local variable Dan Williams
2016-06-28 7:23 ` Bart Van Assche
2016-06-28 8:14 ` Richard Weinberger [this message]
2016-06-28 11:58 ` Christoph Hellwig
2016-06-27 19:30 ` [PATCH v5 4/5] block: convert to device_add_disk() Dan Williams
2016-06-28 7:36 ` Bart Van Assche
2016-06-28 11:58 ` Christoph Hellwig
2016-06-27 19:30 ` [PATCH v5 5/5] block: remove ->driverfs_dev Dan Williams
2016-06-28 7:30 ` Bart Van Assche
2016-06-28 11:59 ` Christoph Hellwig
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=577231CF.6000301@nod.at \
--to=richard@nod.at \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jdike@addtoit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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;
as well as URLs for NNTP newsgroup(s).