From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chuhong Yuan <hslester96@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Oded Gabbay <oded.gabbay@gmail.com>,
Tomas Winkler <tomas.winkler@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: Use dev_get_drvdata where possible
Date: Tue, 23 Jul 2019 14:26:54 +0200 [thread overview]
Message-ID: <20190723122654.GA11835@kroah.com> (raw)
In-Reply-To: <20190723121949.22021-1-hslester96@gmail.com>
On Tue, Jul 23, 2019 at 08:19:49PM +0800, Chuhong Yuan wrote:
> Instead of using to_pci_dev + pci_get_drvdata,
> use dev_get_drvdata to make code simpler.
>
> Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
> ---
> drivers/misc/cardreader/alcor_pci.c | 6 ++----
> drivers/misc/habanalabs/habanalabs_drv.c | 6 ++----
> drivers/misc/mei/pci-me.c | 19 ++++++++-----------
> drivers/misc/mei/pci-txe.c | 19 ++++++++-----------
> 4 files changed, 20 insertions(+), 30 deletions(-)
Please break this up into one-patch-per driver so that they can go
through the various different maintainers of them.
thanks,
greg k-h
prev parent reply other threads:[~2019-07-23 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 12:19 [PATCH] misc: Use dev_get_drvdata where possible Chuhong Yuan
2019-07-23 12:26 ` Greg Kroah-Hartman [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=20190723122654.GA11835@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=hslester96@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.com \
--cc=tomas.winkler@intel.com \
/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).