From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vasileios Amoiridis <vassilisamir@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, ang.iglesiasg@gmail.com,
linus.walleij@linaro.org, biju.das.jz@bp.renesas.com,
javier.carrasco.cruz@gmail.com, semen.protsenko@linaro.org,
579lpy@gmail.com, ak@it-klinger.de, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v4 2/7] iio: pressure: bmp280: Add support for bmp280 soft reset
Date: Thu, 29 Aug 2024 23:18:25 +0300 [thread overview]
Message-ID: <ZtDXkZQh689PGtrb@smile.fi.intel.com> (raw)
In-Reply-To: <20240829190004.GB3493@vamoiridPC>
On Thu, Aug 29, 2024 at 09:00:04PM +0200, Vasileios Amoiridis wrote:
> On Thu, Aug 29, 2024 at 03:10:22PM +0300, Andy Shevchenko wrote:
> > On Wed, Aug 28, 2024 at 10:51:22PM +0200, Vasileios Amoiridis wrote:
...
> > Yes, it's up to 84 characters long, but I think it improves readability.
>
> In all the previous cases though, shouldn't checkpatch.pl generate errors?
No, much earlier than 100 characters relaxed limit was introduced, checkpatch
stopped complaining on long string literals.
> I didn't notice that they were below 80 chars and I never checked more
> because checkpatch.pl didn't say anything...
Exactly! This is old (6+ years?) feature.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-08-29 20:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 20:51 [PATCH v4 0/7] pressure: bmp280: Minor cleanup and interrupt support Vasileios Amoiridis
2024-08-28 20:51 ` [PATCH v4 1/7] iio: pressure: bmp280: Use bulk read for humidity calibration data Vasileios Amoiridis
2024-08-29 12:06 ` Andy Shevchenko
2024-08-29 18:57 ` Vasileios Amoiridis
2024-08-28 20:51 ` [PATCH v4 2/7] iio: pressure: bmp280: Add support for bmp280 soft reset Vasileios Amoiridis
2024-08-29 12:10 ` Andy Shevchenko
2024-08-29 19:00 ` Vasileios Amoiridis
2024-08-29 20:18 ` Andy Shevchenko [this message]
2024-08-28 20:51 ` [PATCH v4 3/7] iio: pressure: bmp280: Remove config error check for IIR filter updates Vasileios Amoiridis
2024-08-28 20:51 ` [PATCH v4 4/7] iio: pressure: bmp280: Use sleep and forced mode for oneshot captures Vasileios Amoiridis
2024-08-29 12:31 ` Andy Shevchenko
2024-08-29 19:13 ` Vasileios Amoiridis
2024-08-29 20:26 ` Andy Shevchenko
2024-08-28 20:51 ` [PATCH v4 5/7] dt-bindings: iio: pressure: bmp085: Add interrupts for BMP3xx and BMP5xx devices Vasileios Amoiridis
2024-08-29 6:06 ` Krzysztof Kozlowski
2024-08-29 19:15 ` Vasileios Amoiridis
2024-08-28 20:51 ` [PATCH v4 6/7] iio: pressure: bmp280: Add data ready trigger support Vasileios Amoiridis
2024-08-29 12:40 ` Andy Shevchenko
2024-08-29 19:19 ` Vasileios Amoiridis
2024-08-31 11:04 ` Jonathan Cameron
2024-08-28 20:51 ` [PATCH v4 7/7] iio: pressure: bmp280: Move bmp085 interrupt to new configuration Vasileios Amoiridis
2024-08-29 12:42 ` Andy Shevchenko
2024-08-29 19:20 ` Vasileios Amoiridis
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=ZtDXkZQh689PGtrb@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=579lpy@gmail.com \
--cc=ak@it-klinger.de \
--cc=ang.iglesiasg@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=vassilisamir@gmail.com \
/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).