From: Andreas Kemnade <andreas@kemnade.info>
To: Dhruv Menon <dhruvmenon1104@gmail.com>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
"Raghavendra, Vignesh" <vigneshr@ti.com>,
andi.shyti@kernel.org, Janusz Krzysztofik <jmkrzyszt@gmail.com>,
tony Lindgren <tony@atomide.com>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] i2c: omap: Cleaned up coding style and parameters
Date: Tue, 3 Dec 2024 23:04:53 +0100 [thread overview]
Message-ID: <20241203230453.1280ed4a@akair> (raw)
In-Reply-To: <Z07QLveHUQlvDfIt@melbuntu>
Am Tue, 3 Dec 2024 15:02:30 +0530
schrieb Dhruv Menon <dhruvmenon1104@gmail.com>:
> This patch has been splitted into two parts,
>
> 1. [PATCH v2 1/2] i2c: omap: Clean up coding style
> 2. [PATCH v2 2/2] i2c: omap: Removed unused parameter
>
> The patchset also removed the changes regarding msleep as the
> adjustment was relatively minor which was added earlier. The
> change was initially considered based on "Timer's howto"
> documentation which recommends to change any msleep(x) < 10ms
> to usleep_range(x*1000, x*2000) for better precision.
>
> Thank you for the time and review. I look forward to your feedback
>
send the output inline, see
Documentation/process/submitting-patches.rst:
No MIME, no links, no compression, no attachments. Just plain text
Also we want imperative mood in the patches.
There is also a lot of automated processing of these patch emails.
Regards,
Andreas
next prev parent reply other threads:[~2024-12-03 22:05 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 [this message]
2024-12-03 7:35 ` [PATCH] " Andreas Kemnade
2024-12-03 7:59 ` 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=20241203230453.1280ed4a@akair \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=andi.shyti@kernel.org \
--cc=dhruvmenon1104@gmail.com \
--cc=hns@goldelico.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 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.