From: Chris Wright Subject: Re: [PATCH] xen block: remove driver_data direct access of struct device Date: Thu, 30 Apr 2009 15:35:35 -0700 Message-ID: <20090430223535.GO3036@sequoia.sous-sol.org> References: <20090430222448.GA18690@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20090430222448.GA18690@kroah.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Greg Kroah-Hartman Cc: Chris Wright , virtualization@lists.osdl.org, xen-devel@lists.xensource.com, Greg KH List-Id: virtualization@lists.linuxfoundation.org * Greg Kroah-Hartman (gregkh@suse.de) wrote: > In the near future, the driver core is going to not allow direct access > to the driver_data pointer in struct device. Instead, the functions > dev_get_drvdata() and dev_set_drvdata() should be used. These functions > have been around since the beginning, so are backwards compatible with > all older kernel versions. > > Cc: xen-devel@lists.xensource.com > Cc: virtualization@lists.osdl.org > Cc: Chris Wright > Cc: Jeremy Fitzhardinge > Signed-off-by: Greg Kroah-Hartman Acked-by: Chris Wright after... > - dev->dev.driver_data = NULL; > + dev_det_drvdata(&dev->dev, NULL); ...fixing your fingers/script so it compiles ;-)