From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-input@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] input: remove driver_data direct access of struct device
Date: Fri, 1 May 2009 06:30:03 -0700 [thread overview]
Message-ID: <20090501133003.GA20000@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20090430221730.GA18512@kroah.com>
On Thu, Apr 30, 2009 at 03:17:30PM -0700, Greg Kroah-Hartman wrote:
> From: Greg Kroah-Hartman <gregkh@suse.de>
>
> 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.
>
Applied to my 'next' branch, thanks Greg.
--
Dmitry
prev parent reply other threads:[~2009-05-01 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 22:17 [PATCH] input: remove driver_data direct access of struct device Greg Kroah-Hartman
2009-05-01 13:30 ` Dmitry Torokhov [this message]
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=20090501133003.GA20000@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-input@vger.kernel.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).