From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] i2c: smbus: don't abuse loop variable
Date: Thu, 28 Jan 2021 10:15:43 +0100 [thread overview]
Message-ID: <20210128091543.GH963@ninjato> (raw)
In-Reply-To: <20210112151230.46518-2-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
On Tue, Jan 12, 2021 at 04:12:29PM +0100, Wolfram Sang wrote:
> Don't use 'i' to carry data, make a specific variable for it. After the
> move to memcpy recently, we can even remove 'i'.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-28 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 15:12 [PATCH 0/2] i2c: smbus: small cleanups in emulation function Wolfram Sang
2021-01-12 15:12 ` [PATCH 1/2] i2c: smbus: don't abuse loop variable Wolfram Sang
2021-01-28 9:15 ` Wolfram Sang [this message]
2021-01-12 15:12 ` [PATCH 2/2] i2c: smbus: improve naming in i2c_smbus_xfer_emulated() Wolfram Sang
2021-01-28 9:15 ` 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=20210128091543.GH963@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@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).