From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Andy Shevchenko <andy@infradead.org>,
Hans de Goede <hdegoede@redhat.com>,
Darren Hart <dvhart@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] usb: roles: intel_xhci: Supplying software node for the role mux
Date: Wed, 4 Sep 2019 14:37:21 +0200 [thread overview]
Message-ID: <20190904123721.GB5043@kroah.com> (raw)
In-Reply-To: <20190819100724.30051-3-heikki.krogerus@linux.intel.com>
On Mon, Aug 19, 2019 at 01:07:23PM +0300, Heikki Krogerus wrote:
> The primary purpose for this node will be to allow linking
> the users of the switch to it. The users will be for example
> USB Type-C connectors. By supplying a reference to this
> node in the software nodes representing the USB Type-C
> controllers or connectors, the drivers for those devices can
> access the switch.
>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2019-09-04 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 10:07 [PATCH v3 0/3] software node: Introduce software_node_find_by_name() Heikki Krogerus
2019-08-19 10:07 ` [PATCH v3 1/3] software node: Add software_node_find_by_name() Heikki Krogerus
2019-09-04 12:37 ` Greg Kroah-Hartman
2019-08-19 10:07 ` [PATCH v3 2/3] usb: roles: intel_xhci: Supplying software node for the role mux Heikki Krogerus
2019-08-19 10:37 ` Andy Shevchenko
2019-09-04 12:37 ` Greg Kroah-Hartman [this message]
2019-08-19 10:07 ` [PATCH v3 3/3] platform/x86: intel_cht_int33fe: Use new API to gain access to the role switch Heikki Krogerus
2019-08-19 10:39 ` [PATCH v3 0/3] software node: Introduce software_node_find_by_name() Andy Shevchenko
2019-08-19 10:41 ` Rafael J. Wysocki
2019-08-19 12:46 ` 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=20190904123721.GB5043@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.