From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andy Shevchenko <andy@infradead.org>,
Hans de Goede <hdegoede@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Darren Hart <dvhart@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] software node: Introduce software_node_find_by_name()
Date: Mon, 19 Aug 2019 12:41:57 +0200 [thread overview]
Message-ID: <CAJZ5v0i7snXodEg0iO0yUaQgg=3o9gGKDed1Kd6V2Y4hgygWKQ@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VfivaaAz1s5AD0BxcTCyO3P0yJUajKh0=WJ6f4w1XkHPg@mail.gmail.com>
On Mon, Aug 19, 2019 at 12:39 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Mon, Aug 19, 2019 at 1:08 PM Heikki Krogerus
> <heikki.krogerus@linux.intel.com> wrote:
> >
> > Hi,
> >
> > There was still one bug spotted by Andy in v2. The role switch node
> > was not removed in case of an error (patch 2/3). It is now fixed.
>
> It would be nice to have immutable branch for these changes. There is
> at least some other activity regard to intel_cht_int33fe driver.
When they land in my devprop branch, that will be immutable.
next prev parent reply other threads:[~2019-08-19 10:42 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
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 [this message]
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='CAJZ5v0i7snXodEg0iO0yUaQgg=3o9gGKDed1Kd6V2Y4hgygWKQ@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@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).