All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: Vadim Pasternak <vadimp@nvidia.com>, linux-i2c@vger.kernel.org
Subject: Re: [PATCH i2c-next v5 0/6] mux: mlxcpld: Extend driver functionality
Date: Tue, 9 Feb 2021 11:38:43 +0100	[thread overview]
Message-ID: <20210209103843.GA9698@ninjato> (raw)
In-Reply-To: <e86e396b-b099-5174-ae0a-393401b1e767@axentia.se>

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

On Mon, Feb 08, 2021 at 10:26:08PM +0100, Peter Rosin wrote:
> Hi!
> 
> On 2021-02-08 21:16, Vadim Pasternak wrote:
> > The patchset adds new features for the existing Mellanox systems.
> > 
> > Patch #1 converts driver to platform driver.
> > Patch #2 prepare driver for word addressing support.
> > Patch #3 removes adapter numbers enforcement.
> > Patch #4 adds support for word address space devices.
> > Patch #5 extends mux number supported by driver.
> > Patch #6 adds callback notification about mux creation.
> > 
> > Vadim Pasternak (6):
> >   i2c: mux: mlxcpld: Convert driver to platform driver
> >   i2c: mux: mlxcpld: Prepare mux selection infrastructure for two-byte
> >     support
> >   i2c: mux: mlxcpld: Get rid of adapter numbers enforcement
> >   i2c: mux: mlxcpld: Extend driver to support word address space devices
> >   i2c: mux: mlxcpld: Extend supported mux number
> >   i2c: mux: mlxcpld: Add callback to notify mux creation completion
> > 
> >  drivers/i2c/muxes/i2c-mux-mlxcpld.c   | 128 ++++++++++++++++++++--------------
> >  include/linux/platform_data/mlxcpld.h |  11 ++-
> >  2 files changed, 83 insertions(+), 56 deletions(-)
> > 
> 
> I am now happy with this series. All looks good and every patch makes sense
> on its own. Thank you for putting in the effort!

All applied to for-next, thanks everyone!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2021-02-09 10:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 20:16 [PATCH i2c-next v5 0/6] mux: mlxcpld: Extend driver functionality Vadim Pasternak
2021-02-08 20:16 ` [PATCH i2c-next v5 1/6] i2c: mux: mlxcpld: Convert driver to platform driver Vadim Pasternak
2021-02-08 21:26   ` Peter Rosin
2021-02-08 20:16 ` [PATCH i2c-next v5 2/6] i2c: mux: mlxcpld: Prepare mux selection infrastructure for two-byte support Vadim Pasternak
2021-02-08 21:26   ` Peter Rosin
2021-02-08 20:16 ` [PATCH i2c-next v5 3/6] i2c: mux: mlxcpld: Get rid of adapter numbers enforcement Vadim Pasternak
2021-02-08 21:26   ` Peter Rosin
2021-02-08 20:16 ` [PATCH i2c-next v5 4/6] i2c: mux: mlxcpld: Extend driver to support word address space devices Vadim Pasternak
2021-02-08 21:27   ` Peter Rosin
2021-02-08 20:16 ` [PATCH i2c-next v5 5/6] i2c: mux: mlxcpld: Extend supported mux number Vadim Pasternak
2021-02-08 21:27   ` Peter Rosin
2021-02-08 20:16 ` [PATCH i2c-next v5 6/6] i2c: mux: mlxcpld: Add callback to notify mux creation completion Vadim Pasternak
2021-02-08 21:27   ` Peter Rosin
2021-02-08 21:26 ` [PATCH i2c-next v5 0/6] mux: mlxcpld: Extend driver functionality Peter Rosin
2021-02-08 22:01   ` Vadim Pasternak
2021-02-09 10:38   ` Wolfram Sang [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=20210209103843.GA9698@ninjato \
    --to=wsa@the-dreams.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=vadimp@nvidia.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.