From: Guenter Roeck <linux@roeck-us.net>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org
Subject: [v2,6/8] usb: typec: fusb302: 2 small misc. fixes
Date: Thu, 7 Mar 2019 10:20:23 -0800 [thread overview]
Message-ID: <20190307182023.GF26282@roeck-us.net> (raw)
On Thu, Mar 07, 2019 at 05:36:05PM +0100, Hans de Goede wrote:
> Fix a copy and paste error in an error message and a spelling error
> in a comment.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/usb/typec/tcpm/fusb302.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/typec/tcpm/fusb302.c b/drivers/usb/typec/tcpm/fusb302.c
> index b74c6ff67aae..23f773d07514 100644
> --- a/drivers/usb/typec/tcpm/fusb302.c
> +++ b/drivers/usb/typec/tcpm/fusb302.c
> @@ -1380,7 +1380,7 @@ static int fusb302_handle_togdone_src(struct fusb302_chip *chip,
> FUSB_REG_MASK_COMP_CHNG);
> if (ret < 0) {
> fusb302_log(chip,
> - "cannot unmask bc_lcl interrupt, ret=%d", ret);
> + "cannot unmask comp_chng interrupt, ret=%d", ret);
> return ret;
> }
> chip->intr_comp_chng = true;
> @@ -1555,7 +1555,7 @@ static irqreturn_t fusb302_irq_intn(int irq, void *dev_id)
> fusb302_log(chip, "IRQ: COMP_CHNG, comp=%s",
> comp_result ? "true" : "false");
> if (comp_result) {
> - /* cc level > Rd_threashold, detach */
> + /* cc level > Rd_threshold, detach */
> chip->cc1 = TYPEC_CC_OPEN;
> chip->cc2 = TYPEC_CC_OPEN;
> tcpm_cc_change(chip->tcpm_port);
> --
> 2.20.1
>
next reply other threads:[~2019-03-07 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 18:20 Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-07 16:36 [v2,6/8] usb: typec: fusb302: 2 small misc. fixes Hans de Goede
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=20190307182023.GF26282@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--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).