From: Thierry Reding <thierry.reding@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] mailbox: tegra-hsp: use devm_kstrdup_const()
Date: Tue, 13 Nov 2018 22:11:44 +0100 [thread overview]
Message-ID: <20181113211144.GC2724@ulmo> (raw)
In-Reply-To: <20181108164610.28361-1-brgl@bgdev.pl>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Thu, Nov 08, 2018 at 05:46:10PM +0100, Bartosz Golaszewski wrote:
> Use devm_kstrdup_const() in the tegra-hsp driver. This mostly serves as
> an example of how to use this new routine to shrink driver code.
>
> Also use devm_kzalloc() instead of regular kzalloc() to shrink the
> driver even more.
>
> Doorbell objects are only removed in the driver's remove callback so
> it's safe to convert all memory allocations to devres.
>
> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
> ---
> drivers/mailbox/tegra-hsp.c | 41 ++++++++-----------------------------
> 1 file changed, 9 insertions(+), 32 deletions(-)
This looks really nice. I'm currently working on a series of patches to
add shared mailboxes to the HSP driver. Part of that series adds struct
device *dev to struct tegra_hsp, which in turn would simplify this
patch a little.
Looking at some of the changes here it also seems like they would
conflict with my patches in some places. Would you mind if I pick this
patch up into my series and resolve the conflicts there?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-13 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 16:46 [PATCH] mailbox: tegra-hsp: use devm_kstrdup_const() Bartosz Golaszewski
2018-11-13 21:11 ` Thierry Reding [this message]
2018-11-14 8:27 ` Bartosz Golaszewski
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=20181113211144.GC2724@ulmo \
--to=thierry.reding@gmail.com \
--cc=brgl@bgdev.pl \
--cc=jassisinghbrar@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@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.