From: Krzysztof Wilczynski <kw@linux.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
"Tomasz Duszynski" <tduszyns@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v3] iio: light: bh1750: Resolve compiler warning and make code more readable
Date: Sun, 15 Sep 2019 20:41:34 +0200 [thread overview]
Message-ID: <20190915184133.GA25817@rocinante> (raw)
In-Reply-To: <20190915104838.0776d2a4@archlinux>
Hello Jonathan,
[...]
> Applied to the togreg branch of iio.git and pushed out as testing
> for the autobuilders to play with it. Added Uwe's Acked-by as well.
Thank you!
> Sorry for the confusing advice I gave earlier, I managed to confuse
> myself on what the original code said.
No problem. :) Uwe suggested to me how to clean things up and word the
commit message more appropriately, thus a very good learning experience
for me.
Thank you again!
Krzysztof
prev parent reply other threads:[~2019-09-15 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 11:31 [PATCH] iio: light: bh1750: Move static keyword to the front of declaration Krzysztof Wilczynski
2019-09-03 17:35 ` Tomasz Duszynski
2019-09-08 10:49 ` Jonathan Cameron
2019-09-08 13:52 ` Krzysztof Wilczynski
2019-09-10 13:35 ` Jonathan Cameron
2019-09-10 20:25 ` Krzysztof Wilczynski
2019-09-10 20:38 ` [PATCH v2] iio: light: bh1750: Resolve compiler warning and make code more readable Krzysztof Wilczynski
2019-09-10 21:04 ` Uwe Kleine-König
2019-09-13 20:24 ` [PATCH v3] " Krzysztof Wilczynski
2019-09-15 9:48 ` Jonathan Cameron
2019-09-15 18:41 ` Krzysztof Wilczynski [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=20190915184133.GA25817@rocinante \
--to=kw@linux.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=tduszyns@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.