From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Chen Yu <chenyu56@huawei.com>, Jun Li <jun.li@nxp.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/9] device connection: Add support for device graphs
Date: Thu, 31 Jan 2019 15:36:14 +0200 [thread overview]
Message-ID: <20190131133614.GB13072@kuha.fi.intel.com> (raw)
In-Reply-To: <07262cf3-c512-d3dd-f383-3795f035a2d5@redhat.com>
On Thu, Jan 31, 2019 at 11:06:29AM +0100, Hans de Goede wrote:
> Hi,
>
> On 30-01-19 17:02, Heikki Krogerus wrote:
> > Hi,
> >
> > This is the second version of this series. On top the two code style
> > improvements requested by Andy, I also renamed the connection
> > identifiers used with the USB Type-C muxes for something that I felt
> > are better, especially after we start using them to name reference
> > device properties in fwnodes. That's why the first patch is now split
> > in two, 1/9 and 3/9.
> >
> > Hans! Please note that there is no functional change. The alt mode
> > device is still getting a handle to the mux, just like before.
>
> Ack.
>
> I've reviewed the entire series and it looks good to me.
>
> Patches 1-3 are:
>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
>
> I'm slightly less familiar with the material in patches 4-9, so they
> are:
>
> Acked-by: Hans de Goede <hdegoede@redhat.com>
>
> I will also add this series to my personal git tree for testing.
Cool!
Thanks Hans!
--
heikki
next prev parent reply other threads:[~2019-01-31 13:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 16:02 Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 1/9] platform/x86: intel_cht_int33fe: Prepare for better mux naming scheme Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 2/9] usb: typec: Rationalize the API for the muxes Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 3/9] platform/x86: intel_cht_int33fe: Remove old style mux connections Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 4/9] device connection: Add fwnode member to struct device_connection Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 5/9] usb: typec: mux: Find the muxes by also matching against the device node Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 6/9] usb: roles: " Heikki Krogerus
2019-02-11 9:58 ` Jun Li
2019-02-11 10:46 ` Heikki Krogerus
2019-02-11 12:40 ` Heikki Krogerus
2019-02-12 6:03 ` Jun Li
2019-02-12 8:50 ` Heikki Krogerus
2019-02-12 10:41 ` Jun Li
2019-02-12 11:24 ` Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 7/9] usb: typec: Find the ports " Heikki Krogerus
2019-01-30 16:51 ` Andy Shevchenko
2019-01-31 13:35 ` Heikki Krogerus
2019-02-11 8:39 ` Heikki Krogerus
2019-02-11 11:52 ` Andy Shevchenko
2019-01-30 16:02 ` [PATCH v2 8/9] device connection: Prepare support for firmware described connections Heikki Krogerus
2019-01-30 16:02 ` [PATCH v2 9/9] device connection: Find device connections also from device graphs Heikki Krogerus
2019-01-31 10:06 ` [PATCH v2 0/9] device connection: Add support for " Hans de Goede
2019-01-31 13:36 ` Heikki Krogerus [this message]
2019-02-12 10:44 ` Jun Li
2019-02-12 11:31 ` 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=20190131133614.GB13072@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=chenyu56@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jun.li@nxp.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
all inboxes | Powered by JetHome®