From: Guenter Roeck <linux@roeck-us.net>
To: Kyle Tso <kyletso@google.com>,
heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org
Cc: badhri@google.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] usb: typec: Comment correction for typec_partner_register_altmode
Date: Mon, 13 Jul 2020 23:48:38 -0700 [thread overview]
Message-ID: <2e840825-f73c-87b7-33d2-9f103a507a80@roeck-us.net> (raw)
In-Reply-To: <20200714033453.4044482-2-kyletso@google.com>
On 7/13/20 8:34 PM, Kyle Tso wrote:
> typec_register_altmode returns ERR_PTR on failure.
>
> Signed-off-by: Kyle Tso <kyletso@google.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/usb/typec/class.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/typec/class.c b/drivers/usb/typec/class.c
> index c9234748537a..02655694f200 100644
> --- a/drivers/usb/typec/class.c
> +++ b/drivers/usb/typec/class.c
> @@ -580,7 +580,7 @@ EXPORT_SYMBOL_GPL(typec_partner_set_identity);
> * SVID listed in response to Discover Modes command need to be listed in an
> * array in @desc.
> *
> - * Returns handle to the alternate mode on success or NULL on failure.
> + * Returns handle to the alternate mode on success or ERR_PTR on failure.
> */
> struct typec_altmode *
> typec_partner_register_altmode(struct typec_partner *partner,
>
next prev parent reply other threads:[~2020-07-14 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 3:34 [PATCH 0/2] tcpm: Error handling for tcpm_register_partner_altmodes Kyle Tso
2020-07-14 3:34 ` [PATCH 1/2] usb: typec: Comment correction for typec_partner_register_altmode Kyle Tso
2020-07-14 6:48 ` Guenter Roeck [this message]
2020-07-28 11:56 ` Heikki Krogerus
2020-07-14 3:34 ` [PATCH 2/2] usb: typec: tcpm: Error handling for tcpm_register_partner_altmodes Kyle Tso
2020-07-14 6:49 ` Guenter Roeck
2020-07-28 11:56 ` Heikki Krogerus
2020-07-14 6:02 ` [PATCH 0/2] " Greg KH
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=2e840825-f73c-87b7-33d2-9f103a507a80@roeck-us.net \
--to=linux@roeck-us.net \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kyletso@google.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;
as well as URLs for NNTP newsgroup(s).