From: Kyle Tso <kyletso@google.com>
To: heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org
Cc: badhri@google.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Kyle Tso <kyletso@google.com>
Subject: [PATCH 0/3] Some fixes for select_usb_power_delivery
Date: Thu, 22 Jun 2023 23:04:20 +0800 [thread overview]
Message-ID: <20230622150423.3726894-1-kyletso@google.com> (raw)
Hi, here are some fixes about the attribute "select_usb_power_delivery"
in typec/class.c
===
usb: typec: Set port->pd before adding device for typec_port
This one is about the visibility of the attribute. port->pd should be
set before device_add otherwise the visibility will be false because
port->pd is NULL.
===
usb: typec: Iterate pds array when showing the pd list
This patch fixes a problem about the incorrect fetching of the pointers
to each usb_power_delivery handle.
===
usb: typec: Use sysfs_emit_at when concatenating the string
This patch changes the use of the API from sysfs_emit to sysfs_emit_at
because the buffer address is not aligned to PAGE_SIZE.
===
Kyle Tso (3):
usb: typec: Set port->pd before adding device for typec_port
usb: typec: Iterate pds array when showing the pd list
usb: typec: Use sysfs_emit_at when concatenating the string
drivers/usb/typec/class.c | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
--
2.41.0.162.gfafddb0af9-goog
next reply other threads:[~2023-06-22 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 15:04 Kyle Tso [this message]
2023-06-22 15:04 ` [PATCH 1/3] usb: typec: Set port->pd before adding device for typec_port Kyle Tso
2023-06-23 7:50 ` Greg KH
2023-06-23 10:08 ` Kyle Tso
2023-06-22 15:04 ` [PATCH 2/3] usb: typec: Iterate pds array when showing the pd list Kyle Tso
2023-06-22 15:04 ` [PATCH 3/3] usb: typec: Use sysfs_emit_at when concatenating the string Kyle Tso
2023-06-23 7:51 ` Greg KH
2023-06-23 10:06 ` Kyle Tso
2023-06-23 10:11 ` Kyle Tso
2023-06-23 11:14 ` Greg KH
2023-06-23 14:23 ` Kyle Tso
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=20230622150423.3726894-1-kyletso@google.com \
--to=kyletso@google.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--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