From: Joerg Roedel <joro@8bytes.org>
To: Fuqian Huang <huangfq.daxian@gmail.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch v2 06/10] iommu: using dev_get_drvdata directly
Date: Thu, 4 Jul 2019 10:12:48 +0200 [thread overview]
Message-ID: <20190704081247.GC6546@8bytes.org> (raw)
In-Reply-To: <20190704023620.4689-1-huangfq.daxian@gmail.com>
On Thu, Jul 04, 2019 at 10:36:20AM +0800, Fuqian Huang wrote:
> #define to_iommu(dev) \
> - ((struct omap_iommu *)platform_get_drvdata(to_platform_device(dev)))
> + ((struct omap_iommu *)dev_get_drvdata(dev))
A similar change is already queued for v5.3.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Fuqian Huang <huangfq.daxian@gmail.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch v2 06/10] iommu: using dev_get_drvdata directly
Date: Thu, 4 Jul 2019 10:12:48 +0200 [thread overview]
Message-ID: <20190704081247.GC6546@8bytes.org> (raw)
In-Reply-To: <20190704023620.4689-1-huangfq.daxian@gmail.com>
On Thu, Jul 04, 2019 at 10:36:20AM +0800, Fuqian Huang wrote:
> #define to_iommu(dev) \
> - ((struct omap_iommu *)platform_get_drvdata(to_platform_device(dev)))
> + ((struct omap_iommu *)dev_get_drvdata(dev))
A similar change is already queued for v5.3.
next prev parent reply other threads:[~2019-07-04 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 2:36 [Patch v2 06/10] iommu: using dev_get_drvdata directly Fuqian Huang
2019-07-04 2:36 ` Fuqian Huang
2019-07-04 8:12 ` Joerg Roedel [this message]
2019-07-04 8:12 ` Joerg Roedel
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=20190704081247.GC6546@8bytes.org \
--to=joro@8bytes.org \
--cc=huangfq.daxian@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@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 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.