From: Darren Hart <dvhart@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Vadim Pasternak <vadimp@mellanox.com>,
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 v6 6/8] platform/mellanox: Introduce support for Mellanox register access driver
Date: Tue, 19 Jun 2018 17:20:25 -0700 [thread overview]
Message-ID: <20180620002025.GC11460@fury> (raw)
In-Reply-To: <b804ccc4-77c3-e7a9-9486-8d12d50ec5f7@infradead.org>
On Sun, Jun 17, 2018 at 09:52:16AM -0700, Randy Dunlap wrote:
> On 06/17/2018 09:56 AM, Vadim Pasternak wrote:
> > diff --git a/drivers/platform/mellanox/Kconfig b/drivers/platform/mellanox/Kconfig
...
> > + space trough sysfs interface. The sets of registers for sysfs access
>
> through
>
> > + are defined per system type bases and includes the registers related
>
> and include the
>
I've taken care of these, thanks Randy, and applied the series to my testing
queue. Once the builds complete, I'll move these to for-next.
Vadim, I see you've already updated the kernel version in the sys documentation
to 4.19, so I won't attempt to push these into the 4.18 RC cycle.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-06-20 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 16:56 [PATCH v6 6/8] platform/mellanox: Introduce support for Mellanox register access driver Vadim Pasternak
2018-06-17 16:52 ` Randy Dunlap
2018-06-20 0:20 ` Darren Hart [this message]
2018-06-20 4:30 ` Vadim Pasternak
2018-06-17 16:56 ` [PATCH v6 7/8] platform/x86: mlx-platform: Add mlxreg-io platform driver activation Vadim Pasternak
2018-06-17 16:56 ` [PATCH v6 8/8] Documentation/ABI: Add documentation mlxreg-io sysfs interfaces Vadim Pasternak
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=20180620002025.GC11460@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=rdunlap@infradead.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