From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Chen Yu <chenyu56@huawei.com>, Jun Li <jun.li@nxp.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/9] device connection: Add support for device graphs
Date: Mon, 18 Feb 2019 09:07:27 +0100 [thread overview]
Message-ID: <20190218080727.GA21246@kroah.com> (raw)
In-Reply-To: <20190215124715.GA10182@kuha.fi.intel.com>
On Fri, Feb 15, 2019 at 02:47:15PM +0200, Heikki Krogerus wrote:
> Hi Greg,
>
> On Thu, Feb 14, 2019 at 11:10:44AM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Feb 13, 2019 at 10:45:48AM +0300, Heikki Krogerus wrote:
> > > Hi,
> > >
> > > This is the third version of my proposal to add device graph parsing
> > > to the device connection API. There was only one problem reported in
> > > v2 by Jun - kernel-doc entry was missing for the new fwnode member in
> > > struct usb_role_switch_desc - and it's now fixed.
> > >
> > > The second version of the series:
> > > https://lkml.org/lkml/2019/1/30/622
> > >
> > > The commit message from v1:
> > >
> > > This series adds support for OF and ACPI device graph parsing to the
> > > device connection API.
> > >
> > > Handling the graph is straightforward, but because I'm adding that
> > > fwnode member to struct device_connection, I had to make sure all the
> > > existing users consider it.
> > >
> > > The plan is to only support matching with fwnode in the future, so no
> > > more device name matching. The software fwnodes that we now have in
> > > kernel should make that possible, once we add support for references
> > > to them.
> > >
> > > The original RFC:
> > > https://lkml.org/lkml/2018/10/24/619
> >
> > All now merged, thanks.
>
> It looks like you have not followed the order of the patches in this
> series.
>
> You applied at least the patch 4/9 ("device connection: Add fwnode
> member to struct device_connection") as the last patch to your
> usb-next branch. The rest of the series, patches starting from 5/9,
> depend on that patch.
Ugh, did I just apply them out of order? I can't rewrite my tree now,
sorry about that, odd that my sorting didn't work.
I think all of the patches are now in the tree, so I didn't miss
anything, is there anything I can do now? Want me to revert them and
then add them back in the correct order?
thanks,
greg k-h
next prev parent reply other threads:[~2019-02-18 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 7:45 Heikki Krogerus
2019-02-13 7:45 ` [PATCH v3 1/9] platform/x86: intel_cht_int33fe: Prepare for better mux naming scheme Heikki Krogerus
2019-02-13 8:34 ` Sergei Shtylyov
2019-02-13 7:45 ` [PATCH v3 2/9] usb: typec: Rationalize the API for the muxes Heikki Krogerus
2019-02-13 7:45 ` [PATCH v3 3/9] platform/x86: intel_cht_int33fe: Remove old style mux connections Heikki Krogerus
2019-02-13 7:45 ` [PATCH v3 4/9] device connection: Add fwnode member to struct device_connection Heikki Krogerus
2019-02-13 7:45 ` [PATCH v3 5/9] usb: typec: mux: Find the muxes by also matching against the device node Heikki Krogerus
2019-02-13 7:45 ` [PATCH v3 6/9] usb: roles: " Heikki Krogerus
2019-02-13 7:45 ` [PATCH v3 7/9] usb: typec: Find the ports " Heikki Krogerus
2019-02-13 8:38 ` Sergei Shtylyov
2019-02-13 7:45 ` [PATCH v3 8/9] device connection: Prepare support for firmware described connections Heikki Krogerus
2019-02-13 7:45 ` [PATCH v3 9/9] device connection: Find device connections also from device graphs Heikki Krogerus
2019-02-14 10:10 ` [PATCH v3 0/9] device connection: Add support for " Greg Kroah-Hartman
2019-02-15 12:47 ` Heikki Krogerus
2019-02-18 8:07 ` Greg Kroah-Hartman [this message]
2019-02-18 8:51 ` 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=20190218080727.GA21246@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=chenyu56@huawei.com \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.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
Powered by JetHome