linux-kernel - Re: [PATCH v3] usb: typec: intel_pmc_mux: Expose IOM port status to debugfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 19 Apr 2023 15:13:28 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Rajat Khandelwal <rajat.khandelwal@...ux.intel.com>
Cc:     heikki.krogerus@...ux.intel.com, linux-usb@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] usb: typec: intel_pmc_mux: Expose IOM port status to
 debugfs

On Wed, Apr 19, 2023 at 06:33:45PM +0530, Rajat Khandelwal wrote:
> IOM status has a crucial role during debugging to check the
> current state of the type-C port.
> There are ways to fetch the status, but all those require the
> IOM port status offset, which could change with platform.
> 
> Make a debugfs directory for intel_pmc_mux and expose the status
> under it per port basis.
> 
> Signed-off-by: Rajat Khandelwal <rajat.khandelwal@...ux.intel.com>
> ---
> 
> v3: Allocate the debugfs directory name for the platform device with
> its ACPI dev name included

{sigh}   No, sorry, this is not correct.

Also, you did not properly follow the rules that all Intel kernel
developers are supposed to follow.  Please consult your local kernel
developer team and do so before sending any more kernel patches out.

greg k-h