From: Darren Hart <dvhart@infradead.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Vadim Pasternak <vadimp@mellanox.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"geert@linux-m68k.org" <geert@linux-m68k.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kvalo@codeaurora.org" <kvalo@codeaurora.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [patch v3] drivers/platform/x86: introduce support for Mellanox hotplug driver
Date: Sun, 23 Oct 2016 07:47:58 -0700 [thread overview]
Message-ID: <20161023144758.GA120221@f23x64.localdomain> (raw)
In-Reply-To: <20161023082353.GA1714@nanopsycho.orion>
On Sun, Oct 23, 2016 at 10:23:53AM +0200, Jiri Pirko wrote:
> Sun, Oct 23, 2016 at 08:14:53AM CEST, vadimp@mellanox.com wrote:
> >
> >
> >> -----Original Message-----
> >> From: Darren Hart [mailto:dvhart@infradead.org]
> >> Sent: Friday, October 21, 2016 9:42 PM
> >> To: Vadim Pasternak <vadimp@mellanox.com>
> >> Cc: davem@davemloft.net; geert@linux-m68k.org; akpm@linux-
> >> foundation.org; kvalo@codeaurora.org; gregkh@linuxfoundation.org;
> >> mchehab@kernel.org; linux@roeck-us.net; linux-kernel@vger.kernel.org;
> >> platform-driver-x86@vger.kernel.org; jiri@resnulli.us
> >> Subject: Re: [patch v3] drivers/platform/x86: introduce support for Mellanox
> >> hotplug driver
> >>
> >> On Thu, Oct 20, 2016 at 04:28:01PM +0000, vadimp@mellanox.com wrote:
> >> > From: Vadim Pasternak <vadimp@mellanox.com>
> >> >
> >> > Enable system support for the Mellanox Technologies hotplug platform
> >> > driver, which provides support for the next Mellanox basic systems:
> >> > "msx6710", "msx6720", "msb7700", "msn2700", "msx1410", "msn2410",
> >> > "msb7800", "msn2740", "msn2100" and also various number of derivative
> >> > systems from the above basic types.
> >> > This driver handles hot-plug events for the power suppliers, power
> >> > cables and fans for the above systems.
> >> >
> >> > The Kconfig currently controlling compilation of this code is:
> >> > driver/platform/x86:config MLX_CPLD_PLATFORM
> >> > tristate "Mellanox platform hotplug driver support"
> >> >
> >> > Signed-off-by: Vadim Pasternak <vadimp@mellanox.com>
> >> > ---
> >> > v1->v2:
> >> > Comments pointed out by Darren:
> >> > - remove whitespaces in config;
> >> > - remove redundant includes for header files;
> >> > - fix comments styling;
> >> > - fix register value assignment in mlxcpld_hotplug_attr_show;
> >> > - mlxcpld_hotplug_attr_init - use local aliases to reduce line
> >> > length;
> >> > - Add fields description in the struct mlxcpld_hotplug_device;
> >> > v2->v3:
> >> > Comments pointed out by Darren:
> >> > - Fix structures and enum comments in mlxcpld-hotplug.c according to
> >> > Documentation/kernel-documentation.rst guideline;
> >> > - Assign and mask aggregation status in mlxcpld_hotplug_work_handler on
> >> > the same line.
> >> > - Refactor mlxcpld_hotplug_work_handler. Make common helper routine for
> >> > each attribute type.
> >> > - Produce error message in case signal is not expected.
> >> > - Fix header file according to Documentation/kernel-documentation.rst
> >> > guideline;
> >>
> >> > Fix added by Vadim:
> >> > Fix re-scheduling flow for possibly missed signals. By mistake it
> >> > was coupled with FAN.
> >>
> >> Thanks Vadim. Merged to for-next for 4.10.
> >>
> >> Also for 4.10, it would be good to move mlx-platform out of arch/x86/platform
> >> to
> >> drivers/platform/x86 as it isn't an architectural driver. Would you be able to
> >> prepare the patch?
> >
> >Hi Darren,
> >
> >Thank you very much for all your reviews.
> >
> >Sure, I'll prepare the patch.
> >
> >Should it be submitted in two different patches (remove in git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git; and add in
> >git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git)?
> >Or in one patch, in git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git?
>
> One patch, please.
It needs to be in one patch, yes. Otherwise you would leave the
platform/driver/x86 side missing it's dependencies... it would be a mess.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2016-10-23 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 16:28 vadimp
2016-10-21 18:42 ` Darren Hart
2016-10-23 6:14 ` Vadim Pasternak
2016-10-23 8:23 ` Jiri Pirko
2016-10-23 14:47 ` Darren Hart [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=20161023144758.GA120221@f23x64.localdomain \
--to=dvhart@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab@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
all inboxes | Powered by JetHome®