From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
Markus Mayer <code@mmayer.net>,
Brian Norris <computersforpeace@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>
Cc: Markus Mayer <mmayer@broadcom.com>,
ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] soc: brcmstb: dpfe: optimize generic_show()
Date: Sat, 9 Mar 2019 14:03:24 -0800 [thread overview]
Message-ID: <20190309220324.26015-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20190212012443.21819-3-code@mmayer.net>
On Mon, 11 Feb 2019 17:24:42 -0800, Markus Mayer <code@mmayer.net> wrote:
> From: Markus Mayer <mmayer@broadcom.com>
>
> We can pass a (struct priv_data *) to generic_show() rather than a
> (struct device *). For two of the three callers of this function, the
> change means one less call to dev_get_drvdata(). For the third caller,
> it makes no difference.
>
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> ---
Applied to drivers/next, thanks!
--
Florian
next prev parent reply other threads:[~2019-03-09 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 1:24 [PATCH 0/3] Some minor updates and fixes for the BRCMSTB DPFE driver Markus Mayer
2019-02-12 1:24 ` [PATCH 1/3] soc: brcmstb: dpfe: use msleep() over udelay() Markus Mayer
2019-03-09 22:03 ` Florian Fainelli
2019-02-12 1:24 ` [PATCH 2/3] soc: brcmstb: dpfe: optimize generic_show() Markus Mayer
2019-03-09 22:03 ` Florian Fainelli [this message]
2019-02-12 1:24 ` [PATCH 3/3] soc: brcmstb: dpfe: use byte 3 of registers MR4-MR8 Markus Mayer
2019-03-09 22:03 ` Florian Fainelli
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=20190309220324.26015-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=code@mmayer.net \
--cc=computersforpeace@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmayer@broadcom.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).