From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Michael Walle" <michael@walle.cc>,
"Daniel Scally" <djrscally@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Len Brown" <lenb@kernel.org>,
"ACPI Devel Maling List" <linux-acpi@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Russell King" <linux@armlinux.org.uk>,
"Horatiu Vultur" <horatiu.vultur@microchip.com>
Subject: Re: [PATCH v4 1/1] device property: Allow error pointer to be passed to fwnode APIs
Date: Tue, 15 Mar 2022 15:27:43 +0200 [thread overview]
Message-ID: <YjCUT3WhNWfrE+VJ@smile.fi.intel.com> (raw)
In-Reply-To: <CAJZ5v0hbY8XCC-DfkoPFe15awV_FOpq91pUZvmZ9JrYi1QBMEg@mail.gmail.com>
On Tue, Mar 15, 2022 at 12:16:01PM +0100, Rafael J. Wysocki wrote:
> On Mon, Mar 14, 2022 at 8:51 PM Michael Walle <michael@walle.cc> wrote:
...
> > This breaks SFP/phylink (using the lan966x switch) on my board. See below
> > for more details.
Michael, thank you for the report, I'll investigate it further.
> I'm dropping this commit for the time being.
Thanks! Fine with me as I think it's not critical (the current or pending users
of the fwnode_find_reference() are / will be aware of the error pointer).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-03-15 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 12:37 [PATCH v4 1/1] device property: Allow error pointer to be passed to fwnode APIs Andy Shevchenko
2022-03-08 14:36 ` Heikki Krogerus
2022-03-08 19:03 ` Rafael J. Wysocki
2022-03-14 19:51 ` Michael Walle
2022-03-15 11:16 ` Rafael J. Wysocki
2022-03-15 13:27 ` Andy Shevchenko [this message]
2022-04-06 13:35 ` Andy Shevchenko
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=YjCUT3WhNWfrE+VJ@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=horatiu.vultur@microchip.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=nuno.sa@analog.com \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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