From: Jean Delvare <jdelvare@suse.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: Use driver name constant instead of function dev_driver_string
Date: Mon, 14 Jun 2021 18:27:57 +0200 [thread overview]
Message-ID: <20210614182757.32c90431@endymion> (raw)
In-Reply-To: <089c47ad-1519-947e-ac31-290da37159d7@gmail.com>
On Tue, 25 May 2021 22:04:23 +0200, Heiner Kallweit wrote:
> We are the driver, so we can use the driver name directly instead of
> retrieving it by calling dev_driver_string().
Makes sense. Should make the code slightly faster.
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> drivers/i2c/busses/i2c-i801.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
> (...)
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Tested-by: Jean Delvare <jdelvare@suse.de>
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2021-06-14 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 20:04 [PATCH] i2c: i801: Use driver name constant instead of function dev_driver_string Heiner Kallweit
2021-06-14 16:27 ` Jean Delvare [this message]
2021-06-20 20:55 ` Wolfram Sang
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=20210614182757.32c90431@endymion \
--to=jdelvare@suse.de \
--cc=hkallweit1@gmail.com \
--cc=linux-i2c@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 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).