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,
michaelsh@mellanox.com, ivecera@redhat.com
Subject: Re: [PATCH v1 0/7] platform/x86: Mellanox add fixes and new features
Date: Fri, 13 Apr 2018 09:17:55 -0700 [thread overview]
Message-ID: <20180413161755.GB27560@fury> (raw)
In-Reply-To: <1522144927-56512-1-git-send-email-vadimp@mellanox.com>
On Tue, Mar 27, 2018 at 10:02:00AM +0000, Vadim Pasternak wrote:
> This patcheset includes:
>
> Document fixes for mlxreg-hotplug driver and mlxreg header file.
>
> Fix for the race condition in mlxreg-hotplug driver.
>
> Adding support for ODM system types.
>
> Activation of Mellanox LED driver from mlx-platform.
>
> Introduction of new mlxreg-io driver.
>
> Activation of mlxreg-io driver from mlx-platform.
Hi Vadim,
As you can see, all the patch names you listed above ^ are automatically
populated by the tooling below. Please use the message in patch 0/7 to
provide the reviewer with contextual information about these changes. A
summary of the series and why its needed is a good start. You want to
keep specific information to each patch with the patch. Think of this as
an Introduction to help the reviewer be prepared to review each
individual patch.
This message provides no context, and no introduction, so a reviewer
will have to figure that out as they go - which is another barrier to
getting the code reviewed.
Something for next time. OK, on to the review...
>
> Vadim Pasternak (7):
> platform_data/mlxreg: Document fixes for hotplug device
> platform/mellanox: mlxreg-hotplug: Document fixes for hotplug private
> data
> platform/mellanox: mlxreg-hotplug: add extra cycle for hotplug work
> queue
> platform: mellanox: add new ODM system types to mlx-platform
> platform/x86: mlx-platform: Add LED platform driver activation
> platform/mellanox: Introduce support for Mellanox register access
> driver
> platform/x86: mlx-platform: Add mlxreg-io platform driver activation
>
> drivers/platform/mellanox/Kconfig | 11 +
> drivers/platform/mellanox/Makefile | 1 +
> drivers/platform/mellanox/mlxreg-hotplug.c | 23 +-
> drivers/platform/mellanox/mlxreg-io.c | 221 ++++++++++++++
> drivers/platform/x86/mlx-platform.c | 447 +++++++++++++++++++++++++++++
> include/linux/platform_data/mlxreg.h | 66 ++++-
> 6 files changed, 765 insertions(+), 4 deletions(-)
> create mode 100644 drivers/platform/mellanox/mlxreg-io.c
>
> --
> 2.1.4
>
>
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-04-13 16:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 10:02 [PATCH v1 0/7] platform/x86: Mellanox add fixes and new features Vadim Pasternak
2018-03-27 10:02 ` [PATCH v1 1/7] platform_data/mlxreg: Document fixes for hotplug device Vadim Pasternak
2018-04-13 16:23 ` Darren Hart
2018-03-27 10:02 ` [PATCH v1 2/7] platform/mellanox: mlxreg-hotplug: Document fixes for hotplug private data Vadim Pasternak
2018-04-13 16:27 ` Darren Hart
2018-03-27 10:02 ` [PATCH v1 3/7] platform/mellanox: mlxreg-hotplug: add extra cycle for hotplug work queue Vadim Pasternak
2018-04-13 16:47 ` Darren Hart
2018-04-13 19:39 ` Vadim Pasternak
2018-03-27 10:02 ` [PATCH v1 4/7] platform: mellanox: add new ODM system types to mlx-platform Vadim Pasternak
2018-04-13 16:54 ` Darren Hart
2018-04-13 19:53 ` Vadim Pasternak
2018-03-27 10:02 ` [PATCH v1 5/7] platform/x86: mlx-platform: Add LED platform driver activation Vadim Pasternak
2018-03-27 10:02 ` [PATCH v1 6/7] platform/mellanox: Introduce support for Mellanox register access driver Vadim Pasternak
2018-03-27 10:02 ` [PATCH v1 7/7] platform/x86: mlx-platform: Add mlxreg-io platform driver activation Vadim Pasternak
2018-04-13 16:17 ` Darren Hart [this message]
2018-05-11 15:28 ` [PATCH v1 0/7] platform/x86: Mellanox add fixes and new features 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=20180413161755.GB27560@fury \
--to=dvhart@infradead.org \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelsh@mellanox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.