public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Dhruv Menon <dhruvmenon1104@gmail.com>,
	vigneshr@ti.com, andi.shyti@kernel.org, jmkrzyszt@gmail.com,
	tony@atomide.com, khilman@baylibre.com, rogerq@kernel.org,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: omap: Cleaned up coding style and parameters
Date: Tue, 3 Dec 2024 08:35:47 +0100	[thread overview]
Message-ID: <20241203083547.0213c054@akair> (raw)
In-Reply-To: <Z04faeJUgZTydiMb@darkstar.musicnaut.iki.fi>

Am Mon, 2 Dec 2024 22:58:17 +0200
schrieb Aaro Koskinen <aaro.koskinen@iki.fi>:

> On Tue, Dec 03, 2024 at 12:22:51AM +0530, Dhruv Menon wrote:
> > This commit addresses the coding style issues present in i2c-omap.c,
> > identified by checkpatch.pl and removes unused parameters present in
> > two functions.
> > 
> > 1. Coding style issues includes Macro Utilization, alignnment
> >    correction, updating ms_sleep() < 20 to usleep_range().
> > 2. Removed unused parameters from omap_i2c_receive_data()
> >    and omap_i2c_transmit_data().
> > 
> > No functional changes have been introduced in this commit.  
> 
> Not sure if that is correct as sleeps can be now shorter? I wouldn't
> touch them unless you can show some real benefit (checkpatch.pl warning
> isn't one for old driver code).
> 
The sleeps are not shorter, instead possibly longer. I do not think
that is an issue, AFAIK the idea with sleep range is to bundle wakeups
and reduce power consumption.

> Maybe also changes should be split into separate patches for easier
> review.
> 
I would leave out omap_i2c_*data() parameter stuff until the i2c irq
regressions are fixed, maybe that parameter is needed.

Regards,
Andreas

  parent reply	other threads:[~2024-12-03  7:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 18:52 [PATCH] i2c: omap: Cleaned up coding style and parameters Dhruv Menon
2024-12-02 20:58 ` Aaro Koskinen
2024-12-03  7:31   ` [PATCH v2] " Dhruv Menon
2024-12-03  8:25     ` H. Nikolaus Schaller
2024-12-03  9:32       ` [PATCH v3] " Dhruv Menon
2024-12-03 22:04         ` Andreas Kemnade
2024-12-03  7:35   ` Andreas Kemnade [this message]
2024-12-03  7:59     ` [PATCH] " Dhruv Menon
2024-12-03  8:09     ` Aaro Koskinen

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=20241203083547.0213c054@akair \
    --to=andreas@kemnade.info \
    --cc=aaro.koskinen@iki.fi \
    --cc=andi.shyti@kernel.org \
    --cc=dhruvmenon1104@gmail.com \
    --cc=jmkrzyszt@gmail.com \
    --cc=khilman@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.com \
    --cc=vigneshr@ti.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