From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Douglas Gilbert <dgilbert@interlog.com>
Subject: Re: [PATCH] hwmon: powerz: add support for ChargerLAB KM002C
Date: Tue, 19 Sep 2023 19:15:25 +0200 [thread overview]
Message-ID: <5fb278c7-df91-4f02-ab5f-baa47d27507f@t-8ch.de> (raw)
In-Reply-To: <6e5eff10-949c-4f17-a3f3-347b85b89e11@roeck-us.net>
On 2023-09-18 12:05:19-0700, Guenter Roeck wrote:
> On Mon, Sep 11, 2023 at 07:44:42AM +0200, Thomas Weißschuh wrote:
> > The KM002C is similar to the KM003C and seems to use the same
> > protocol and firmware.
> >
> > Reported-by: Douglas Gilbert <dgilbert@interlog.com>
> > Closes: https://lore.kernel.org/lkml/290ebce4-54f0-8ac1-2a13-cbc806d80d64@interlog.com/
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
> >
> > This patch is based on hwmon-next,
> > commit 80369d9e1f2f ("hwmon: (sch5627) Document behaviour of limit registers").
> >
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
>
> Applied, but please be more careful with your comments and Signed-off-by:
> tags. There should only be one '---', and one signature.
Thanks,
the duplicate Signed-off-by is indeed an oversight which I'll
try to avoid in the future.
As for the '---':
Two of them are generated by the 'b4' tool and I added one manually with
the hwmon-next information.
For other subsystems this wasn't an issue so far.
Are these duplicate sections a problem for your personal tooling or is
it affecting something more widespread?
I can try to avoid these issues when sending patches to you specifically
or maybe changes in b4 in general are the correct solution.
Thomas
> > ---
> > drivers/hwmon/powerz.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> >
> > ---
> > base-commit: 80369d9e1f2f16993ae6d148553c37bf65a209e4
> > change-id: 20230911-powerz-km002c-94afb4d3d645
> >
> > Best regards,
> >
> > diff --git a/drivers/hwmon/powerz.c b/drivers/hwmon/powerz.c
> > index 2b9693aee6f6..cfb635f94d66 100644
> > --- a/drivers/hwmon/powerz.c
> > +++ b/drivers/hwmon/powerz.c
> > @@ -254,6 +254,7 @@ static void powerz_disconnect(struct usb_interface *intf)
> > }
> >
> > static const struct usb_device_id powerz_id_table[] = {
> > + { USB_DEVICE_INTERFACE_NUMBER(0x5FC9, 0x0061, 0x00) }, /* ChargerLAB POWER-Z KM002C */
> > { USB_DEVICE_INTERFACE_NUMBER(0x5FC9, 0x0063, 0x00) }, /* ChargerLAB POWER-Z KM003C */
> > { }
> > };
next prev parent reply other threads:[~2023-09-19 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 5:44 Thomas Weißschuh
2023-09-18 19:05 ` Guenter Roeck
2023-09-19 17:15 ` Thomas Weißschuh [this message]
2023-09-19 17:24 ` Guenter Roeck
2023-09-19 18:02 ` Konstantin Ryabitsev
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=5fb278c7-df91-4f02-ab5f-baa47d27507f@t-8ch.de \
--to=linux@weissschuh.net \
--cc=dgilbert@interlog.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®