From: Ruslan Babayev <ruslan@babayev.com>
To: mika.westerberg@linux.intel.com, wsa@the-dreams.de,
linux@armlinux.org.uk, andrew@lunn.ch, f.fainelli@gmail.com,
hkallweit1@gmail.com, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [net-next,v4 0/2] Enable SFP on ACPI based systems
Date: Tue, 28 May 2019 16:02:31 -0700 [thread overview]
Message-ID: <20190528230233.26772-1-ruslan@babayev.com> (raw)
Changes:
v2:
- more descriptive commit body
v3:
- made 'i2c_acpi_find_adapter_by_handle' static inline
v4:
- don't initialize i2c_adapter to NULL. Instead see below...
- handle the case of neither DT nor ACPI present as invalid.
- alphabetical includes.
- use has_acpi_companion().
- use the same argument name in i2c_acpi_find_adapter_by_handle()
in both stubbed and non-stubbed cases.
Ruslan Babayev (2):
i2c: acpi: export i2c_acpi_find_adapter_by_handle
net: phy: sfp: enable i2c-bus detection on ACPI based systems
drivers/i2c/i2c-core-acpi.c | 3 ++-
drivers/net/phy/sfp.c | 35 +++++++++++++++++++++++++++--------
include/linux/i2c.h | 6 ++++++
3 files changed, 35 insertions(+), 9 deletions(-)
--
2.19.2
next reply other threads:[~2019-05-28 23:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 23:02 Ruslan Babayev [this message]
2019-05-28 23:02 ` [net-next,v4 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle Ruslan Babayev
2019-05-29 15:49 ` Andrew Lunn
2019-06-02 19:58 ` Wolfram Sang
2019-05-28 23:02 ` [net-next,v4 2/2] net: phy: sfp: enable i2c-bus detection on ACPI based systems Ruslan Babayev
2019-05-29 9:51 ` Russell King - ARM Linux admin
2019-05-29 15:49 ` Andrew Lunn
2019-05-29 9:48 ` [net-next,v4 0/2] Enable SFP " Mika Westerberg
2019-05-29 15:51 ` Andrew Lunn
2019-05-31 6:27 ` Mika Westerberg
2019-05-31 6:48 ` Wolfram Sang
2019-05-31 12:05 ` Andrew Lunn
2019-05-31 12:56 ` Wolfram Sang
2019-05-30 18:27 ` David Miller
2019-05-31 12:57 ` Wolfram Sang
2019-05-31 18:22 ` David Miller
2019-05-31 18:33 ` Russell King - ARM Linux admin
2019-06-01 12:47 ` Wolfram Sang
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=20190528230233.26772-1-ruslan@babayev.com \
--to=ruslan@babayev.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.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 \
/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).