From: Darren Hart <dvhart@infradead.org>
To: Vadim Pasternak <vadimp@mellanox.com>
Cc: andy.shevchenko@gmail.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, jiri@resnulli.us
Subject: Re: [patch v8 0/3] drivers/platform: replace module x86/mlxcpld-hotplug with mellanox/mlxreg-hotplug
Date: Mon, 15 Jan 2018 19:42:09 -0800 [thread overview]
Message-ID: <20180116034209.GA4590@fury> (raw)
In-Reply-To: <1515661123-76604-1-git-send-email-vadimp@mellanox.com>
On Thu, Jan 11, 2018 at 08:58:40AM +0000, Vadim Pasternak wrote:
> The patchset:
> - replaces modules include/linux/platform_data/mlxcpld-hotplug.h and
> drivers/platform/x86/mlxcpld-hotplug.c with the modules
> include/linux/platform_data/mlxreg.h and
> drivers/platform/mellanox/mlxreg-hotplug.c;
> relevant Makefile and Kconfig are updated;
> - modifies Mellanox hotplug driver for making it architecture
> independent. Drivers has been tested for x86 and ARM based systems.
> - introduces regmap interface for mlxreg-hotplug driver to allow hotplug
> event functionality over programmable devices logic, when these devices
> can be attached to different interfaces types, like I2C, LPC, SPI;
> driver drivers/platform/x86/mlx-platform.c is updated according to new
> interface.
Individual review to follow. In general, this series is difficult to
review as it does not present the changes in an incremental fashion. It
appears to have been broken up from a major wholesale re-write. This is
made evident by several stray or out of place changes which are not
consistent with the commit messages and the very large 3/3 patch.
This has waited long enough by no fault of Vadim's, and the impact is
very localized.
Vadim, I'd appreciate it if you would reply to the individual reviews,
and I think I can work with the existing series and tweak a couple
things in the commit messages, and possibly move a Kconfig change to a
different patch, and we can move forward with this.
To follow this email, are two patches which are minor incremental
cleanups, which I'd appreciate your review of before I push them to
testing.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-01-16 3:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 8:58 [patch v8 0/3] drivers/platform: replace module x86/mlxcpld-hotplug with mellanox/mlxreg-hotplug Vadim Pasternak
2018-01-11 8:58 ` [patch v8 1/3] platform/x86: move Mellanox hardware platform hotplug driver to platform/mellanox Vadim Pasternak
2018-01-16 3:42 ` Darren Hart
2018-01-16 8:06 ` Vadim Pasternak
2018-01-17 1:52 ` Darren Hart
2018-01-11 8:58 ` [patch v8 2/3] platform/mellanox: mlxreg-hotplug: allow driver for ARM architecture Vadim Pasternak
2018-01-16 3:43 ` Darren Hart
2018-01-16 8:06 ` Vadim Pasternak
2018-01-17 1:50 ` Darren Hart
2018-01-17 1:53 ` Darren Hart
2018-01-11 8:58 ` [patch v8 3/3] platform/mellanox: mlxreg-hotplug: modify to use regmap intreface Vadim Pasternak
2018-01-16 3:43 ` Darren Hart
2018-01-16 3:42 ` Darren Hart [this message]
2018-01-16 3:45 ` [patch v8 0/3] drivers/platform: replace module x86/mlxcpld-hotplug with mellanox/mlxreg-hotplug Darren Hart
2018-01-16 3:49 ` Darren Hart
2018-01-16 8:08 ` Vadim Pasternak
2018-01-16 3:46 ` Darren Hart
2018-01-16 4:02 ` Darren Hart
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=20180116034209.GA4590@fury \
--to=dvhart@infradead.org \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@mellanox.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