From: Andrew Lunn <andrew@lunn.ch>
To: "Ruslan Babayev (fib)" <fib@cisco.com>
Cc: "20190505220524.37266-2-ruslan@babayev.com"
<20190505220524.37266-2-ruslan@babayev.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"wsa@the-dreams.de" <wsa@the-dreams.de>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>
Subject: Re: [PATCH RFC v2 net-next 2/2] net: phy: sfp: enable i2c-bus detection on ACPI based systems
Date: Fri, 24 May 2019 22:23:23 +0200 [thread overview]
Message-ID: <20190524202323.GS21208@lunn.ch> (raw)
In-Reply-To: <BYAPR11MB33837495646A3A0BB23AD1B4AD000@BYAPR11MB3383.namprd11.prod.outlook.com>
On Wed, May 22, 2019 at 07:29:06PM +0000, Ruslan Babayev (fib) wrote:
> Hi Andrew,
>
> Just wanted to follow up on the patch. Does it look good? Do you have any other feedback, concerns with this patch?
Hi Ruslan
>From what i remember, it is O.K.
I will review it again when you repost it.
Andrew
prev parent reply other threads:[~2019-05-24 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 22:05 [PATCH net-next 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle Ruslan Babayev
2019-05-07 0:35 ` [PATCH RFC v2 net-next] Enable SFP support on ACPI Ruslan Babayev
2019-05-07 0:35 ` [PATCH RFC v2 net-next 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle Ruslan Babayev
2019-05-07 0:35 ` [PATCH RFC v2 net-next 2/2] net: phy: sfp: enable i2c-bus detection on ACPI based systems Ruslan Babayev
2019-05-07 2:38 ` Andrew Lunn
2019-05-07 3:15 ` Ruslan Babayev (fib)
2019-05-22 19:29 ` Ruslan Babayev (fib)
2019-05-24 20:23 ` Andrew Lunn [this message]
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=20190524202323.GS21208@lunn.ch \
--to=andrew@lunn.ch \
--cc=20190505220524.37266-2-ruslan@babayev.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fib@cisco.com \
--cc=hkallweit1@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mika.westerberg@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=wsa@the-dreams.de \
--cc=xe-linux-external@cisco.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;
as well as URLs for NNTP newsgroup(s).