linux-kernel - Re: [PATCH v3 1/4] usb: typec: ucsi: Clean up UCSI_CABLE

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: <2024022923-disloyal-tactless-09ca@gregkh>
Date: Thu, 29 Feb 2024 06:52:26 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Jameson Thies <jthies@...gle.com>
Cc: heikki.krogerus@...ux.intel.com, linux-usb@...r.kernel.org,
	pmalani@...omium.org, bleung@...gle.com,
	abhishekpandit@...omium.org, andersson@...nel.org,
	dmitry.baryshkov@...aro.org, fabrice.gasnier@...s.st.com,
	hdegoede@...hat.com, neil.armstrong@...aro.org,
	rajaram.regupathy@...el.com, saranya.gopal@...el.com,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Benson Leung <bleung@...omium.org>
Subject: Re: [PATCH v3 1/4] usb: typec: ucsi: Clean up UCSI_CABLE_PROP macros

On Thu, Feb 29, 2024 at 01:52:21AM +0000, Jameson Thies wrote:
> Clean up UCSI_CABLE_PROP macros by fixing a bitmask shifting error for
> plug type and updating the modal support macro for consistent naming.
> 
> Fixes: 3cf657f07918 ("usb: typec: ucsi: Remove all bit-fields")
> Cc: stable@...r.kernel.org
> Reviewed-by: Benson Leung <bleung@...omium.org>
> Reviewed-by: Prashant Malani <pmalani@...omium.org>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
> Signed-off-by: Jameson Thies <jthies@...gle.com>
> ---
> Changes in v3:
> - Fixed CC stable.

I see two different copies of this patch on the list, which one is
correct?

And none of them are properly "threaded", so that our tools can't pick
them up at once, can you use 'git send-email' to do this, or do replies
by hand if you aren't using it, so that things will work properly on our
end?  Right now all of these look like individual changes :(

thanks,

greg k-h