From: Greg KH <greg@kroah.com>
To: Patryk <pbiel7@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Question regarding appropriate mailing list
Date: Tue, 3 Sep 2024 19:24:31 +0200 [thread overview]
Message-ID: <2024090324-primp-legume-66a7@gregkh> (raw)
In-Reply-To: <CA+DkFDYQ85nA72X-zkQmdARp-x=JEaovRM8iiKp3PBsuGGJQ4g@mail.gmail.com>
On Tue, Sep 03, 2024 at 06:26:17PM +0200, Patryk wrote:
> Hi,
> What would be the most appropriate mailing list to ask about pmbus
> drivers and power management devices like ltc29**. I'm trying to
> bring-up some LTC devices using existing drivers and I've encountered
> some problems while reading e.g. temp1_max_alarm attribute (NACK
> returned from the target device). I've found what exact line of code
> introduced in 5.15.x kernel causes this problem but I'm not sure
> whether or not that line was added according to the pmbus
> specification expectations therefore the code is fine, but it may that
> it's the device that responds incorrectly and it's behaviour does not
> adhere to the pmbus specification.
Just run scripts/get_maintainer.pl on the files you are looking at and
it will tell you the mailing lists and people to cc: about them.
For example, if you have issues with the driver core functions in
drivers/usb/serial/visor.c, you can do:
$ ./scripts/get_maintainer.pl --file drivers/usb/serial/visor.c
Johan Hovold <johan@kernel.org> (maintainer:USB SERIAL SUBSYSTEM)
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:USB SUBSYSTEM)
linux-usb@vger.kernel.org (open list:USB SERIAL SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
Hope this helps,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2024-09-03 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 16:26 Question regarding appropriate mailing list Patryk
2024-09-03 17:24 ` Greg KH [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=2024090324-primp-legume-66a7@gregkh \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=pbiel7@gmail.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).