From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3A50DCD37A9 for ; Tue, 3 Sep 2024 17:24:46 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.97.1) (envelope-from ) id 1slXGe-000000004Bk-3ld8; Tue, 03 Sep 2024 13:24:36 -0400 Received: from nyc.source.kernel.org ([2604:1380:45d1:ec00::3]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1slXGd-000000004Bd-3rHi for kernelnewbies@kernelnewbies.org; Tue, 03 Sep 2024 13:24:35 -0400 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id D4DF2A43401; Tue, 3 Sep 2024 17:24:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5E4C5C4CEC4; Tue, 3 Sep 2024 17:24:34 +0000 (UTC) Date: Tue, 3 Sep 2024 19:24:31 +0200 From: Greg KH To: Patryk Subject: Re: Question regarding appropriate mailing list Message-ID: <2024090324-primp-legume-66a7@gregkh> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org 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 (maintainer:USB SERIAL SUBSYSTEM) Greg Kroah-Hartman (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