From: Cezar Chiru <chiru.cezar.89@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Andi Shyti <andi.shyti@kernel.org>
Cc: peda@axentia.se, jdelvare@suse.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: Main i2c-*.c files and algos/ subdirectory : Fix errors and warnings generated by checkpatch
Date: Thu, 4 Sep 2025 04:08:36 +0300 [thread overview]
Message-ID: <aLjmlHDPV9n88YoM@hangmanPC> (raw)
In-Reply-To: <aLh3rVYItYZ3CYpq@shikoro>
On Wed, Sep 03, 2025 at 07:15:25PM +0200, Wolfram Sang wrote:
> On Wed, Sep 03, 2025 at 06:56:12PM +0200, Andi Shyti wrote:
> > Hi Cezar,
> >
> > On Sat, Aug 30, 2025 at 12:30:15PM +0300, Cezar Chiru wrote:
> > > Fixed some coding style errors and warnings plus some minor changes
> > > in code as reported by checkpatch script. The busses/ and muxes/
> > > subfolders will be dealt with another commit. Main changes were done
> > > to comments, defines of 'if' statement, swapping 'unsigned' with
> > > 'unsigned int' and other minor changes.
> > >
> > > Signed-off-by: Cezar Chiru <chiru.cezar.89@gmail.com>
> > > ---
> > > drivers/i2c/Kconfig | 2 +-
> > > drivers/i2c/algos/i2c-algo-bit.c | 29 +++++++++------
> > > drivers/i2c/algos/i2c-algo-pca.c | 25 +++++++++----
> > > drivers/i2c/algos/i2c-algo-pcf.c | 61 ++++++++++++++++++++++----------
> > > drivers/i2c/algos/i2c-algo-pcf.h | 10 +++---
> > > drivers/i2c/i2c-boardinfo.c | 2 +-
> > > drivers/i2c/i2c-core-base.c | 59 +++++++++++++++++++-----------
> > > drivers/i2c/i2c-dev.c | 47 ++++++++++++++----------
> > > drivers/i2c/i2c-mux.c | 1 +
> > > drivers/i2c/i2c-slave-eeprom.c | 2 +-
> > > drivers/i2c/i2c-smbus.c | 2 +-
> > > drivers/i2c/i2c-stub.c | 29 +++++++--------
> > > 12 files changed, 170 insertions(+), 99 deletions(-)
> >
> > first of all, thanks for your patch, but I can't accept it.
> > Please split your patch in several smaller patches with single
> > changes.
> >
> > Granularity is very important for reviews and git blame.
>
> Same comment as previous patch: describe testing please
>
Hello Andi, Wolfram,
Resending email to entire receipients in plain text mode from my mutt
client with linux-i2c@vger.kernel.org and linux-kernel@vger.kernel.org
as my initial reply was rejected because of Gmail client being not in plain mode. I thought maybe you didn't receive it. sorry if I sent twice or three times the same message .
I am new to submitting linux kernel patches. The first patch i
submitted "[PATCH] Fix checkpatch.pl warnings and errors in i2c driver
directory and subdirectories" was wrong and also missed
signed--off--by git signature. Some change i made originally broke the
build . I rushed and sent it before I built the kernel and modules.
rookie mistake.
But on the second patch I submitted, I built the kernel and modules
after i made the changes and fixed the build errors. I activated all
i2c external modules and built in modules in the .config under Device
Drivers---> I2C in the menuconfig. But didn't tested the kernel on my
linux laptop and didn't loaded all the external modules to see if they
generate dmesg errors.
I plan to resubmit and break down changes from 1 commit to several
commits(patches) as Andi suggested. I will create a commit in git
explaining how the patches apply (their order) and this patch can be
disregarded. And along with it i will send 1 patch for each i2c file
i submit changes for. Also after I commit locally on git the final
version of the commits I will create a build with everything under
Device Drivers---> I2C menuconfig activated. Upon success I will locally
test the build on my laptop. load manually all external i2c modules and
make sure there aren't any dmesg errors and modules are loaded
successfully. Other than that I don't own any I2C hardware device that
I could test with my laptop.
Wolfram, Andi, if you have other ideas on how i could test the i2c
functionality to make sure i don't break anything with my changes
please let me know.
I am a newbie to linux kernel development and want to take it slow
with small changes in the beginning and then possibly to grow this in
a full time Linux Kernel Developer career.
I will be back to you with next patches by Sunday night this week.
Sorry for the long email but I wanted you to know the whole process
I did to submit the patches.
Best regards,
Cezar Chiru
next prev parent reply other threads:[~2025-09-04 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 9:30 [PATCH] i2c: Main i2c-*.c files and algos/ subdirectory : Fix errors and warnings generated by checkpatch Cezar Chiru
2025-09-03 16:56 ` Andi Shyti
2025-09-03 17:15 ` Wolfram Sang
2025-09-04 1:08 ` Cezar Chiru [this message]
[not found] ` <CANvS2vUf=kOdGKTcy8XWz2aO2uHTf7TkF-EQSedMSYE863oFcA@mail.gmail.com>
2025-09-04 0:28 ` Cezar Chiru
2025-09-04 12:37 ` Andi Shyti
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=aLjmlHDPV9n88YoM@hangmanPC \
--to=chiru.cezar.89@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=wsa+renesas@sang-engineering.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