From: Ali Tariq <alitariq45892@gmail.com>
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: hal.feng@starfivetech.com, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v2] pinctrl: starfive: use dynamic GPIO base allocation
Date: Sun, 26 Oct 2025 02:29:11 +0500 [thread overview]
Message-ID: <0881d989-c1f7-484f-a5e6-aee47ee5c5d6@gmail.com> (raw)
In-Reply-To: <CAJM55Z-SrU1Mk4xUZTgey-zArYAvtpftTwGBb_VEb0zL3L1EPw@mail.gmail.com>
Hi Emil,
Thanks for the review and feedback.
Quoting Emil Renner Berthing:
> 1) The justification for why this is no longer needed should be in
the commit
> message, and not just in a random thread that will soon be forgotten.
My apologies for the confusion. I did add the removal of unused
variables as a bullet point in the v2 changelog (which is in the email
body), but I failed to include the necessary justification for this
removal in the main commit message itself.
You are correct, the justification for removing `gc_base` and associated
macros (because we now use `sfp->gc.base = -1` for dynamic allocation)
belongs in the permanent commit message.
I will update the v2 commit message to clearly state the removal of
macros and unused definitions (before "Signed-off-by") in the v3 submission.
Quoting Emil Renner Berthing:
> 2) Please don't send new revisions as replies. Start a new mail thread.
Understood. I will send the next revision as a new thread.
Quoting Emil Renner Berthing:
> The code changes look good though, so once that is fixed you can add
>
> Reviewed-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
Understood. I will include your Reviewed-by tag in the v3 patch.
Thanks again for the review!
-Ali
prev parent reply other threads:[~2025-10-25 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 18:16 [PATCH] " Ali Tariq
2025-10-22 7:23 ` Bartosz Golaszewski
2025-10-23 12:18 ` Emil Renner Berthing
2025-10-24 14:33 ` [PATCH v2] " Ali Tariq
2025-10-25 10:52 ` Emil Renner Berthing
2025-10-25 21:29 ` Ali Tariq [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=0881d989-c1f7-484f-a5e6-aee47ee5c5d6@gmail.com \
--to=alitariq45892@gmail.com \
--cc=brgl@bgdev.pl \
--cc=emil.renner.berthing@canonical.com \
--cc=hal.feng@starfivetech.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®