public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Heikki Krogerus <heikki.krogeurs@linux.intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, Abel Vesa <abel.vesa@linaro.org>,
	Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH 2/2] usb: typec: ucsi: glink: be more precise on orientation-aware ports
Date: Thu, 7 Nov 2024 06:18:48 +0100	[thread overview]
Message-ID: <2024110729-trunks-hangup-01b5@gregkh> (raw)
In-Reply-To: <20241106-ucsi-glue-fixes-v1-2-d0183d78c522@linaro.org>

On Wed, Nov 06, 2024 at 05:45:55PM +0200, Dmitry Baryshkov wrote:
> Instead of checking if any of the USB-C ports have orientation GPIO and
> thus is orientation-aware, check for the GPIO for the port being
> registered.

What is the visible affect of this change?

Does it fix an existing bug?

thanks,

greg k-h

  parent reply	other threads:[~2024-11-07  5:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 15:45 [PATCH 0/2] usb: typec: ucsi: glink: fix and improve orientation handling Dmitry Baryshkov
2024-11-06 15:45 ` [PATCH 1/2] usb: typec: ucsi: glink: fix off-by-one in connector_status Dmitry Baryshkov
2024-11-07  5:17   ` Greg Kroah-Hartman
2024-11-07 11:04     ` Dmitry Baryshkov
2024-11-07  8:36   ` neil.armstrong
2024-11-08 15:56   ` Johan Hovold
2024-11-06 15:45 ` [PATCH 2/2] usb: typec: ucsi: glink: be more precise on orientation-aware ports Dmitry Baryshkov
2024-11-06 17:13   ` Abel Vesa
2024-11-07  5:18   ` Greg Kroah-Hartman [this message]
2024-11-07 10:02     ` Dmitry Baryshkov
2024-11-07  8:37   ` neil.armstrong
2024-11-08 15:57   ` Johan Hovold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024110729-trunks-hangup-01b5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=abel.vesa@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=heikki.krogeurs@linux.intel.com \
    --cc=johan+linaro@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox