From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] i2c: omap: switch to dev_get_drvdata()
Date: Thu, 9 Jul 2015 21:46:17 +0200 [thread overview]
Message-ID: <20150709194616.GG4744@katana> (raw)
In-Reply-To: <1435260890-32335-1-git-send-email-balbi@ti.com>
On Thu, Jun 25, 2015 at 02:34:48PM -0500, Felipe Balbi wrote:
> there's no need to fetch the platform_device
> in order to dereference it back to the dev
> pointer to access drvdata, we can use
> dev_get_drvdata() instead.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
Applied to for-next, thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150709/92c65ddd/attachment.sig>
prev parent reply other threads:[~2015-07-09 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 19:34 [PATCH 1/3] i2c: omap: switch to dev_get_drvdata() Felipe Balbi
2015-06-25 19:34 ` [PATCH 2/3] i2c: omap: abolish variable name confusion Felipe Balbi
2015-07-09 19:49 ` Wolfram Sang
2015-07-10 17:27 ` Felipe Balbi
2015-07-13 20:38 ` [PATCH 1/3] i2c: omap: switch to dev_get_drvdata() Felipe Balbi
2015-07-13 20:38 ` [PATCH 2/3] i2c: omap: abolish variable name confusion Felipe Balbi
2015-07-13 20:38 ` [PATCH 3/3] i2c: omap: on ->remove() call pm_runtime_put_sync() Felipe Balbi
2015-07-14 11:02 ` [PATCH 1/3] i2c: omap: switch to dev_get_drvdata() Wolfram Sang
2015-06-25 19:34 ` [PATCH 3/3] i2c: omap: on ->remove() call pm_runtime_put_sync() Felipe Balbi
2015-07-09 10:18 ` Alexander Sverdlin
2015-07-09 10:09 ` [PATCH 1/3] i2c: omap: switch to dev_get_drvdata() Alexander Sverdlin
2015-07-09 19:46 ` Wolfram Sang [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=20150709194616.GG4744@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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