linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Vadim Pasternak <vadimp@mellanox.com>
Cc: andy.shevchenko@gmail.com, gregkh@linuxfoundation.org,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, jiri@resnulli.us,
	michaelsh@mellanox.com
Subject: Re: [PATCH v1 0/4] platform/x86: mlx-platform: Add bus differed and auto detection functionalities
Date: Thu, 15 Feb 2018 17:32:37 -0800	[thread overview]
Message-ID: <20180216013237.GC5786@fury> (raw)
In-Reply-To: <1518559776-188942-1-git-send-email-vadimp@mellanox.com>

On Tue, Feb 13, 2018 at 10:09:32PM +0000, Vadim Pasternak wrote:
> This patchset:
> - Adds define for the channels number for mux device.
> - Adds differed bus functionality.
> - Changes input for device create routine in mlxreg-hotplug driver.
> - Adds physical bus number auto detection.

Hi Vadim,

We are now in the RC cycle for 4.16. Do you consider these changes to be
"fixes" that need to be included in 4.16? It was difficult to tell from
the commit messages how severe some of the possible issues were.

I'm concerned about the level of testing seen by the previous patch
series if we are getting these changes so soon after they were merged.
Can you comment on why these are being discovered now - and how
confident are we in the drivers with these changes applied?

> 
> Vadim Pasternak (4):
>   platform/x86: mlx-platform: Use define for the channel numbers
>   platform/x86: mlx-platform: Add differed bus functionality
>   platform/mellanox: mlxreg-hotplug: Change input for device create
>     routine
>   platform/x86: mlx-platform: Add physical bus number auto detection
> 
>  drivers/platform/mellanox/mlxreg-hotplug.c | 31 +++++++++-----
>  drivers/platform/x86/mlx-platform.c        | 68 ++++++++++++++++++++++++++++--
>  include/linux/platform_data/mlxreg.h       |  4 ++
>  3 files changed, 90 insertions(+), 13 deletions(-)
> 
> -- 
> 2.1.4
> 
> 

-- 
Darren Hart
VMware Open Source Technology Center

  parent reply	other threads:[~2018-02-16  1:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 22:09 [PATCH v1 0/4] platform/x86: mlx-platform: Add bus differed and auto detection functionalities Vadim Pasternak
2018-02-13 22:09 ` [PATCH v1 1/4] platform/x86: mlx-platform: Use define for the channel numbers Vadim Pasternak
2018-02-13 22:09 ` [PATCH v1 2/4] platform/x86: mlx-platform: Add differed bus functionality Vadim Pasternak
2018-03-21 22:58   ` Darren Hart
2018-03-22  9:04     ` Greg KH
2018-03-22 22:18       ` Darren Hart
2018-03-22 22:39         ` Greg KH
2018-02-13 22:09 ` [PATCH v1 3/4] platform/mellanox: mlxreg-hotplug: Change input for device create routine Vadim Pasternak
2018-02-13 22:09 ` [PATCH v1 4/4] platform/x86: mlx-platform: Add physical bus number auto detection Vadim Pasternak
2018-02-16  1:32 ` Darren Hart [this message]
2018-02-17  5:08   ` [PATCH v1 0/4] platform/x86: mlx-platform: Add bus differed and auto detection functionalities Vadim Pasternak
2018-03-22 23:55 ` Darren Hart
2018-03-23 15:59   ` Vadim Pasternak
2018-03-23 23:09     ` 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=20180216013237.GC5786@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=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 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).