linux-kernel - Re: [PATCH v1] usb: typec: tcpm: apply vbus before data bringup in tcpm_src

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]

Message-ID: <2025050933-flanking-poison-1d8a@gregkh>
Date: Fri, 9 May 2025 16:44:56 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: RD Babiera <rdbabiera@...gle.com>
Cc: heikki.krogerus@...ux.intel.com, badhri@...gle.com,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: [PATCH v1] usb: typec: tcpm: apply vbus before data bringup in
 tcpm_src_attach

On Tue, May 06, 2025 at 10:57:10AM -0700, RD Babiera wrote:
> On Thu, May 1, 2025 at 8:41 AM Greg KH <gregkh@...uxfoundation.org> wrote:
> 
> > Does not apply to my tree, can you rebase against usb-next and resend?
> 
> This patch is rebased against usb-next/usb-next, but I think I do need to rebase
> against usb-linus. commit 8a50da849151e7e12b43c1d8fe7ad302223aef6b is
> present in usb-next but not usb-linus, and my patch as it is now is
> dependent on it.
> 
> Would you prefer that I rebase against usb-linus and resubmit given
> I'm submitting
> as a stable fix? It looks like the conflicting patch would be up for
> the 6.16 merge
> window.

It depends on when you want it merged, for 6.15-final, or 6.16-final.
Your choice.

thanks,

greg k-h