From: "Nuno Sá" <noname.nuno@gmail.com>
To: Lee Jones <lee@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: nuno.sa@analog.com, linux-gpio@vger.kernel.org,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-input@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Liu Ying" <victor.liu@nxp.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v5 00/20] mfd: adp5585: support keymap events and drop legacy Input driver
Date: Tue, 01 Jul 2025 14:42:46 +0100 [thread overview]
Message-ID: <d60c08a3b518e12c8fc0d0eba4ed208aafa8ca82.camel@gmail.com> (raw)
In-Reply-To: <20250701133732.GO10134@google.com>
On Tue, 2025-07-01 at 14:37 +0100, Lee Jones wrote:
> On Tue, 01 Jul 2025, Laurent Pinchart wrote:
>
> > On Tue, Jul 01, 2025 at 12:09:11PM +0100, Nuno Sá wrote:
> > > On Tue, 2025-07-01 at 12:05 +0100, Lee Jones wrote:
> > > > On Fri, 27 Jun 2025, Nuno Sá wrote:
> > > >
> > > > > On Thu, 2025-06-19 at 14:38 +0100, Lee Jones wrote:
> > > > > > On Sat, 14 Jun 2025, Nuno Sá via B4 Relay wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Here it goes v4. Main changes is to drop chip info based struct
> > > > > > > and
> > > > > > > directly use an enum in the FW .data pointer, use the notifier API
> > > > > > > for
> > > > > > > dispatching events and multiple calls to mfd_add_devices().
> > > > > > >
> > > > > > > Regarding the last point, I think I could have used multiple calls
> > > > > > > to
> > > > > > > devm_mfd_add_devices() and avoid those gotos in
> > > > > > > adp5585_add_devices()
> > > > > > > but I do not feel that would have been "correct".
> > > > > > >
> > > > > > > Thanks!
> > > > > > > - Nuno Sá
> > > > > > >
> > > > > > > ---
> > > > > > > Changes in v5:
> > > > > >
> > > > > > In future, these should be inside the patches themselves please.
> > > > >
> > > > > Hi Lee,
> > > > >
> > > > > I'm about to send v6. I just have a question regarding the above. Do
> > > > > you
> > > > > mean to
> > > > > have the log in the commit message itself like DRM or do it with git
> > > > > notes?
> > > >
> > > > I have no idea what git notes is.
> > >
> > > It pretty much adds a note before the diff stat but with an annoying
> > > "Notes:"
> > > line. b4 seems to ignore it anyways.
> > >
> > > > Simply place the Changelog inside the patch, just above the diff stat.
> > >
> > > There's already some emails about this on v6. I ended up doing it DRM
> > > style
> > > because tweaking the patch before sensing is surprisingly non trivial with
> > > b4.
> > > Unless I missed something.
> >
> > You can record the changelog in the commit message below a
> >
> > ---
> >
> > line asyou modify commits. That way you won't have to write the
> > changelogs when sending the patches, and b4 should not cause any issue.
>
> Exactly this. Should be easy enough.
Yes, just checked now. I was being mistaken by the fact that doing the above
while changing commits will still locally display on my 'git log'. But it will
then be discarded when you apply the patches.
I'll send v7 with the changelog fixed.
- Nuno Sá
next prev parent reply other threads:[~2025-07-01 13:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 14:35 [PATCH v5 00/20] mfd: adp5585: support keymap events and drop legacy Input driver Nuno Sá via B4 Relay
2025-06-14 14:35 ` [PATCH v5 01/20] dt-bindings: mfd: adp5585: ease on the required properties Nuno Sá via B4 Relay
2025-06-14 14:35 ` [PATCH v5 02/20] mfd: adp5585: only add devices given in FW Nuno Sá via B4 Relay
2025-06-14 14:35 ` [PATCH v5 03/20] mfd: adp5585: enable oscilator during probe Nuno Sá via B4 Relay
2025-06-18 17:41 ` Uwe Kleine-König
2025-06-14 14:35 ` [PATCH v5 04/20] mfd: adp5585: make use of MFD_CELL_NAME() Nuno Sá via B4 Relay
2025-06-14 14:35 ` [PATCH v5 05/20] dt-bindings: mfd: adp5585: document adp5589 I/O expander Nuno Sá via B4 Relay
2025-06-14 14:35 ` [PATCH v5 06/20] mfd: adp5585: refactor how regmap defaults are handled Nuno Sá via B4 Relay
2025-06-19 14:19 ` Lee Jones
2025-06-14 14:35 ` [PATCH v5 07/20] mfd: adp5585: add support for adp5589 Nuno Sá via B4 Relay
2025-06-14 14:35 ` [PATCH v5 08/20] mfd: adp5585: add a per chip reg struture Nuno Sá via B4 Relay
2025-06-14 14:36 ` [PATCH v5 09/20] gpio: adp5585: add support for the adp5589 expander Nuno Sá via B4 Relay
2025-06-16 7:57 ` Bartosz Golaszewski
2025-06-14 14:36 ` [PATCH v5 10/20] pwm: adp5585: add support for adp5589 Nuno Sá via B4 Relay
2025-06-18 17:42 ` Uwe Kleine-König
2025-06-14 14:36 ` [PATCH v5 11/20] dt-bindings: mfd: adp5585: add properties for input events Nuno Sá via B4 Relay
2025-06-14 14:36 ` [PATCH v5 12/20] mfd: adp5585: add support for event handling Nuno Sá via B4 Relay
2025-06-14 14:36 ` [PATCH v5 13/20] mfd: adp5585: support reset and unlock events Nuno Sá via B4 Relay
2025-06-14 14:36 ` [PATCH v5 14/20] mfd: adp5585: add support for input devices Nuno Sá via B4 Relay
2025-06-14 14:36 ` [PATCH v5 15/20] gpio: adp5585: support gpi events Nuno Sá via B4 Relay
2025-06-14 14:36 ` [PATCH v5 16/20] Input: adp5585: Add Analog Devices ADP5585/89 support Nuno Sá via B4 Relay
2025-06-17 21:10 ` Dmitry Torokhov
2025-06-14 14:36 ` [PATCH v5 17/20] Input: adp5589: remove the driver Nuno Sá via B4 Relay
2025-06-14 14:36 ` [PATCH v5 18/20] mfd: adp5585: support getting vdd regulator Nuno Sá via B4 Relay
2025-06-19 14:22 ` Lee Jones
2025-06-14 14:36 ` [PATCH v5 19/20] dt-bindings: mfd: adp5585: document reset gpio Nuno Sá via B4 Relay
2025-06-14 14:36 ` [PATCH v5 20/20] mfd: adp5585: add support for a reset pin Nuno Sá via B4 Relay
2025-06-19 13:38 ` [PATCH v5 00/20] mfd: adp5585: support keymap events and drop legacy Input driver Lee Jones
2025-06-27 15:46 ` Nuno Sá
2025-07-01 11:05 ` Lee Jones
2025-07-01 11:09 ` Nuno Sá
2025-07-01 11:15 ` Krzysztof Kozlowski
2025-07-01 11:19 ` Laurent Pinchart
2025-07-01 13:37 ` Lee Jones
2025-07-01 13:42 ` Nuno Sá [this message]
2025-06-19 14:23 ` Lee Jones
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=d60c08a3b518e12c8fc0d0eba4ed208aafa8ca82.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=ukleinek@kernel.org \
--cc=victor.liu@nxp.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).