linux-kernel - Re: [PATCH 0/2] add vendor hooks for usb suspend and resume

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y5mGoXdEIvLqHYnh@kroah.com>
Date:   Wed, 14 Dec 2022 09:17:37 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Puma Hsu <pumahsu@...gle.com>
Cc:     mka@...omium.org, dianders@...omium.org, albertccwang@...gle.com,
        raychi@...gle.com, howardyen@...gle.com, leejj@...gle.com,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] add vendor hooks for usb suspend and resume

On Wed, Dec 14, 2022 at 03:06:48PM +0800, Puma Hsu wrote:
> In mobile, a co-processor can be used for USB audio. When the co-processor
> is working for USB audio, the co-processor is the user/owner of the USB
> driver, and the ACPU is able to sleep in such condition to improve power
> consumption. In order to support this, we need to create vendor hooks in
> suspend and resume functions, and also upload our implementations for
> reference.
> 
> Puma Hsu (2):
>   usb: core: add vendor hook for usb suspend and resume
>   usb: core: add implementations for usb suspend/resume hooks
> 
>  drivers/usb/core/Makefile              |  2 +-
>  drivers/usb/core/driver.c              | 36 +++++++++++++
>  drivers/usb/core/usb-hooks-impl-goog.c | 72 ++++++++++++++++++++++++++
>  drivers/usb/core/usb.h                 |  5 ++
>  4 files changed, 114 insertions(+), 1 deletion(-)
>  create mode 100644 drivers/usb/core/usb-hooks-impl-goog.c
> 
> -- 
> 2.39.0.rc1.256.g54fd8350bd-goog
> 

What differs from the previous submissions of this patch series that
were rejected?  Were the changes that were asked for from those
submissions resolved properly here?

Dropping patches on us every 6 months that were previously rejected with
no description of what changed is a sure way to get them rejected again
:(

thanks,

greg k-h