From: Marcelo Diop-Gonzalez <marcgonzalez@google.com>
To: gregkh@linuxfoundation.org, eric@anholt.net, wahrenst@gmx.net
Cc: devel@driverdev.osuosl.org, linux-rpi-kernel@lists.infradead.org
Subject: [PATCH 0/2] Remove global struct vchiq_drvdata variables
Date: Mon, 11 Nov 2019 12:14:22 -0500 [thread overview]
Message-ID: <cover.1573482698.git.marcgonzalez@google.com> (raw)
These appear to be populated once in vchiq_probe() and then read
once in vchiq_platform_init(), so by moving the logic to that
function we can remove some (small amount of) global data.
Marcelo Diop-Gonzalez (2):
staging: vchiq: Move retrieval of rpi_firmware to
vchiq_platform_init()
staging: vchiq: Remove global bcm*_drvdata
.../interface/vchiq_arm/vchiq_2835_arm.c | 18 ++++++++--
.../interface/vchiq_arm/vchiq_arm.c | 34 ++-----------------
.../interface/vchiq_arm/vchiq_arm.h | 5 ---
3 files changed, 17 insertions(+), 40 deletions(-)
--
2.20.1
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2019-11-11 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 17:14 Marcelo Diop-Gonzalez [this message]
2019-11-11 17:14 ` [PATCH 1/2] staging: vchiq: Move retrieval of rpi_firmware to vchiq_platform_init() Marcelo Diop-Gonzalez
2019-11-12 23:09 ` Greg KH
2019-11-12 23:29 ` Marcelo Diop-Gonzalez
2019-11-13 5:32 ` Greg KH
2019-11-13 14:08 ` Marcelo Diop-Gonzalez
2019-11-13 20:29 ` Marcelo Diop-Gonzalez
2019-11-13 18:17 ` Dan Carpenter
2019-11-13 19:58 ` Marcelo Diop-Gonzalez
2019-11-11 17:14 ` [PATCH 2/2] staging: vchiq: Remove global bcm*_drvdata Marcelo Diop-Gonzalez
2019-11-13 18:18 ` Dan Carpenter
2019-11-13 18:40 ` Stefan Wahren
2019-11-13 19:56 ` Marcelo Diop-Gonzalez
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=cover.1573482698.git.marcgonzalez@google.com \
--to=marcgonzalez@google.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=wahrenst@gmx.net \
/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).