From: Hans de Goede <hdegoede@redhat.com>
To: Kyle Tso <kyletso@google.com>,
linux@roeck-us.net, 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 v6 0/3] AMS, Collision Avoidance, and Protocol Error
Date: Fri, 15 Jan 2021 11:40:29 +0100 [thread overview]
Message-ID: <46d0f968-0fe6-3ce2-420d-d1a4d9042d79@redhat.com> (raw)
In-Reply-To: <20210114145053.1952756-1-kyletso@google.com>
Hi All,
On 1/14/21 3:50 PM, Kyle Tso wrote:
> v5 https://lore.kernel.org/r/20210105163927.1376770-1-kyletso@google.com
>
> "usb: typec: tcpm: AMS and Collision Avoidance"
> - removed the signed-off
> - modified the coding style suggested from Heikki
> - added FR_SWAP AMS handling
>
> "usb: typec: tcpm: Protocol Error handling"
> - removed the signed-off
> - modified the coding style suggested from Heikki
> - modified more coding style problems (line wrapping limit)
>
> "usb: typec: tcpm: Respond Wait if VDM state machine is running"
> - no change
I'm afraid that my testing of this patch-set has been delayed due to a
5.11 regression which I'm chasing down. I have put a task for this
in my calendar for Wednesday Jan 20.
Regards,
Hans
next prev parent reply other threads:[~2021-01-15 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 14:50 Kyle Tso
2021-01-14 14:50 ` [PATCH v6 1/3] usb: typec: tcpm: AMS and Collision Avoidance Kyle Tso
2021-01-14 14:50 ` [PATCH v6 2/3] usb: typec: tcpm: Protocol Error handling Kyle Tso
2021-01-14 14:50 ` [PATCH v6 3/3] usb: typec: tcpm: Respond Wait if VDM state machine is running Kyle Tso
2021-01-15 10:40 ` Hans de Goede [this message]
2021-01-20 13:45 ` [PATCH v6 0/3] AMS, Collision Avoidance, and Protocol Error Hans de Goede
2021-01-20 17:17 ` Greg KH
2021-01-21 7:30 ` Heikki Krogerus
2021-01-23 19:59 ` Guenter Roeck
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=46d0f968-0fe6-3ce2-420d-d1a4d9042d79@redhat.com \
--to=hdegoede@redhat.com \
--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 \
--cc=linux@roeck-us.net \
/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
all inboxes | Powered by JetHome®