From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 1/2] i2c: robotfuzz-osif: remove pointless local variable
Date: Thu, 24 May 2018 22:15:55 +0200 [thread overview]
Message-ID: <20180524201555.x6ayvjjayfqmjvma@ninjato> (raw)
In-Reply-To: <20180509194658.29106-1-peda@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
On Wed, May 09, 2018 at 09:46:57PM +0200, Peter Rosin wrote:
> Just use the value directly instead of assigning it to a
> variable first. And then drop the unused variable.
>
> Signed-off-by: Peter Rosin <peda@axentia.se>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-05-24 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 19:46 [PATCH 1/2] i2c: robotfuzz-osif: remove pointless local variable Peter Rosin
2018-05-09 19:46 ` [PATCH 2/2] i2c: robotfuzz-osif: drop pointless test Peter Rosin
2018-05-24 20:17 ` Wolfram Sang
2018-05-24 20:15 ` Wolfram Sang [this message]
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=20180524201555.x6ayvjjayfqmjvma@ninjato \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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).