All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
	"axboe@fb.com" <axboe@fb.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [GIT PULL] ->driverfs_dev removal for 4.8
Date: Fri, 8 Jul 2016 16:05:12 -0600	[thread overview]
Message-ID: <57802398.2010105@kernel.dk> (raw)
In-Reply-To: <1468015016.19315.10.camel@intel.com>

On 07/08/2016 03:56 PM, Williams, Dan J wrote:
> Hi Jens, please pull from:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm for-4.8/block
>
> ...to receive:
>
> The removal of ->driverfs_dev in favor of just passing the parent
> device in as a parameter to add_disk().  See below, it has received a
> "Reviewed-by" from Christoph, Bart, and Johannes.
>
> It is also a pre-requisite for Fam Zheng's work to cleanup gendisk
> uevents vs attribute visibility [1].  We would extend device_add_disk()
> to take an attribute_group list.
>
> This is based off a branch of block.git/for-4.8/drivers and has
> received a positive build success notification from the kbuild robot
> across several configs.
>
> [1]: "gendisk: Generate uevent after attribute available"
> http://marc.info/?l=linux-virtualization&m=146725201522201&w=2

Pulled, thanks Dan.

-- 
Jens Axboe

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
	"axboe@fb.com" <axboe@fb.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] ->driverfs_dev removal for 4.8
Date: Fri, 8 Jul 2016 16:05:12 -0600	[thread overview]
Message-ID: <57802398.2010105@kernel.dk> (raw)
In-Reply-To: <1468015016.19315.10.camel@intel.com>

On 07/08/2016 03:56 PM, Williams, Dan J wrote:
> Hi Jens, please pull from:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm for-4.8/block
>
> ...to receive:
>
> The removal of ->driverfs_dev in favor of just passing the parent
> device in as a parameter to add_disk().  See below, it has received a
> "Reviewed-by" from Christoph, Bart, and Johannes.
>
> It is also a pre-requisite for Fam Zheng's work to cleanup gendisk
> uevents vs attribute visibility [1].  We would extend device_add_disk()
> to take an attribute_group list.
>
> This is based off a branch of block.git/for-4.8/drivers and has
> received a positive build success notification from the kbuild robot
> across several configs.
>
> [1]: "gendisk: Generate uevent after attribute available"
> http://marc.info/?l=linux-virtualization&m=146725201522201&w=2

Pulled, thanks Dan.

-- 
Jens Axboe

  reply	other threads:[~2016-07-08 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 21:56 [GIT PULL] ->driverfs_dev removal for 4.8 Williams, Dan J
2016-07-08 21:56 ` Williams, Dan J
2016-07-08 22:05 ` Jens Axboe [this message]
2016-07-08 22:05   ` 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=57802398.2010105@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=axboe@fb.com \
    --cc=dan.j.williams@intel.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 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.