public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Rex Nie <rex.nie@jaguarmicro.com>
Cc: bryan.odonoghue@linaro.org, heikki.krogerus@linux.intel.com,
	linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, angus.chen@jaguarmicro.com
Subject: Re: [PATCH] usb: typec: qcom-pmic: fix uninitialized value hdr_len and txbuf_len
Date: Tue, 29 Oct 2024 03:30:38 +0100	[thread overview]
Message-ID: <2024102927-colossal-shore-0f46@gregkh> (raw)
In-Reply-To: <20241029021823.1978-1-rex.nie@jaguarmicro.com>

On Tue, Oct 29, 2024 at 10:18:23AM +0800, Rex Nie wrote:
> If the read of USB_PDPHY_RX_ACKNOWLEDGE_REG failed, then hdr_len and
> txbuf_len are uninitialized. It makes no sense to print message header
> and payload. It is also not safe to print uninitialized length of ram.
> 
> Signed-off-by: Rex Nie <rex.nie@jaguarmicro.com>

What commit id does this fix?

thanks,

greg k-h

  reply	other threads:[~2024-10-29  2:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  2:18 [PATCH] usb: typec: qcom-pmic: fix uninitialized value hdr_len and txbuf_len Rex Nie
2024-10-29  2:30 ` Greg KH [this message]
2024-10-29  6:28   ` 答复: " Rex Nie
2024-10-29 15:28 ` Bjorn Andersson
2024-10-29 15:38   ` Bryan O'Donoghue
2024-10-30  2:27 ` [PATCH v2] usb: typec: qcom-pmic: init value of hdr_len/txbuf_len earlier Rex Nie
2024-10-30  8:39   ` Heikki Krogerus
2024-10-30 10:35     ` 答复: " Rex Nie
2024-10-30 10:32   ` [PATCH v3] " Rex Nie
2024-10-30 12:31     ` Bryan O'Donoghue
2024-10-30 13:19     ` Heikki Krogerus
2024-10-30 13:37       ` 答复: " Rex Nie
2024-10-30 13:36   ` [PATCH v4] " Rex Nie
2024-10-31 10:56     ` Heikki Krogerus
2024-11-01 15:45     ` Bjorn Andersson
2024-11-02 12:27       ` 答复: " Rex Nie

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=2024102927-colossal-shore-0f46@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=angus.chen@jaguarmicro.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rex.nie@jaguarmicro.com \
    /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