From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 4/4] driver core: Add fwnode member to struct device_connection
Date: Tue, 27 Nov 2018 17:07:56 +0200 [thread overview]
Message-ID: <20181127150756.GV10650@smile.fi.intel.com> (raw)
In-Reply-To: <20181127143237.GA22859@kuha.fi.intel.com>
On Tue, Nov 27, 2018 at 04:32:37PM +0200, Heikki Krogerus wrote:
> On Tue, Nov 27, 2018 at 05:28:55PM +0300, Heikki Krogerus wrote:
> > This will prepare the device connection API for connections
> > described in firmware.
>
> This one does not belong to this series, sorry. Please skip it, or if
> you prefer, I'll resend.
Please, resend. It would reduce amount of confusion,
Otherwise the series looks good to me.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-11-27 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 14:28 [PATCH v4 0/3] device property: Add fwnode_get_name() helper Heikki Krogerus
2018-11-27 14:28 ` [PATCH v4 1/4] device property: Introduce fwnode_get_name() Heikki Krogerus
2018-11-27 14:28 ` [PATCH v4 2/4] ACPI: property: Add acpi_fwnode_name() Heikki Krogerus
2018-11-27 14:28 ` [PATCH v4 3/4] of/property: Add of_fwnode_name() Heikki Krogerus
2018-11-27 14:28 ` [PATCH v4 4/4] driver core: Add fwnode member to struct device_connection Heikki Krogerus
2018-11-27 14:32 ` Heikki Krogerus
2018-11-27 15:07 ` Andy Shevchenko [this message]
2018-11-28 8:34 ` 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=20181127150756.GV10650@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=robh@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