linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Vadim Pasternak <vadimp@nvidia.com>, Peter Rosin <peda@axentia.se>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [Re-send: PATCH i2c-next 0/6] i2c: mux: mlxcpld: Extend driver functionality and update licenses
Date: Tue, 5 Jan 2021 11:27:19 +0100	[thread overview]
Message-ID: <20210105102719.GH2000@ninjato> (raw)
In-Reply-To: <20201118144416.184120-1-vadimp@nvidia.com>

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

On Wed, Nov 18, 2020 at 04:44:10PM +0200, Vadim Pasternak wrote:
> The patchset adds new features for the existing Mellanox systems.
> 
> Patches #1-#2 update license to SPDX-License.
> Patch #3  moves header file out of x86 realm.
> Patch #4 converts driver to platform driver.
> Patch #5 adds support for word address space devices.
> Patch #6 extends mux number supported by driver.

Hi Peter,

I hope you had a good start in 2021 and all things are good. Do you have
time to review this series in the near future?

Kind regards,

   Wolfram


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

  parent reply	other threads:[~2021-01-05 10:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 14:44 [Re-send: PATCH i2c-next 0/6] i2c: mux: mlxcpld: Extend driver functionality and update licenses Vadim Pasternak
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 1/6] i2c: mux: mlxcpld: Update module license Vadim Pasternak
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 2/6] platform/x86: " Vadim Pasternak
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 3/6] i2c: mux: mlxcpld: Move header file out of x86 realm Vadim Pasternak
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 4/6] i2c: mux: mlxcpld: Convert driver to platform driver Vadim Pasternak
2021-01-07  7:52   ` Peter Rosin
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 5/6] i2c: mux: mlxcpld: Extend driver to support word address space devices Vadim Pasternak
2021-01-07 10:03   ` Peter Rosin
2021-01-07 20:43     ` Vadim Pasternak
2021-01-08  8:02       ` Peter Rosin
2021-01-11 18:11         ` Vadim Pasternak
2021-01-11 21:22           ` Peter Rosin
2021-01-11 23:24             ` Vadim Pasternak
2021-01-12  9:35               ` Peter Rosin
2021-01-12 10:11                 ` wsa
2021-01-14  7:49                   ` Peter Rosin
2021-01-14 18:43                     ` Vadim Pasternak
2021-01-14 21:10                       ` Peter Rosin
2021-01-14 21:13                         ` Vadim Pasternak
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 6/6] i2c: mux: mlxcpld: Extend supported mux number Vadim Pasternak
2021-01-07 10:10   ` Peter Rosin
2021-01-05 10:27 ` Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-18 13:49 [Re-send: PATCH i2c-next 0/6] i2c: mux: mlxcpld: Extend driver functionality and update licenses Vadim Pasternak
2020-11-18 14:40 ` Wolfram Sang
2020-11-18 14:45   ` 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=20210105102719.GH2000@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 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).