From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/6] typec changes
Date: Tue, 11 Feb 2020 04:25:26 -0800 [thread overview]
Message-ID: <20200211122526.GH1856500@kroah.com> (raw)
In-Reply-To: <20200211112531.86510-1-heikki.krogerus@linux.intel.com>
On Tue, Feb 11, 2020 at 02:25:25PM +0300, Heikki Krogerus wrote:
> Hi Greg,
>
> Here all the "trivial" changes I have for the USB Type-C class at this
> stage. The first patch I already send before [1]. You told me to leave
> the checks in, so I did. The rest of the patches in that series were
> about USB4, which I'm not including here. I decided to propose them
> separately.
>
> The third patch in this series make's it possible to swap the power
> role even when USB Power Delivery is not supported since the latest
> specification now allows it. The rest of the patches are cleanups.
>
> Let me know if you want me to change anything.
Are these fixes for 5.6-rc2 or for new stuff for 5.7-rc1?
thanks,
greg k-h
next prev parent reply other threads:[~2020-02-11 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 11:25 [PATCH 0/6] typec changes Heikki Krogerus
2020-02-11 11:25 ` [PATCHv2 1/6] usb: typec: Make the attributes read-only when writing is not possible Heikki Krogerus
2020-02-11 11:25 ` [PATCH 2/6] usb: typec: Hide the port_type attribute when it's not supported Heikki Krogerus
2020-02-11 11:25 ` [PATCH 3/6] usb: typec: Allow power role swapping even without USB PD Heikki Krogerus
2020-02-11 11:25 ` [PATCH 4/6] usb: typec: Fix the description of struct typec_capability Heikki Krogerus
2020-02-11 11:25 ` [PATCH 5/6] usb: typec: altmode: Remove the notification chain Heikki Krogerus
2020-02-11 11:25 ` [PATCH 6/6] usb: typec: mux: Drop support for device name matching Heikki Krogerus
2020-02-11 12:25 ` Greg Kroah-Hartman [this message]
2020-02-11 12:30 ` [PATCH 0/6] typec changes Heikki Krogerus
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=20200211122526.GH1856500@kroah.com \
--to=gregkh@linuxfoundation.org \
--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).