From: Wolfram Sang <wsa@the-dreams.de>
To: Vadim Pasternak <vadimp@nvidia.com>
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: Wed, 18 Nov 2020 15:40:47 +0100 [thread overview]
Message-ID: <20201118144047.GA2649@kunai> (raw)
In-Reply-To: <20201118134957.182779-1-vadimp@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 174 bytes --]
On Wed, Nov 18, 2020 at 03:49:51PM +0200, Vadim Pasternak wrote:
> The patchset adds new features for the existing Mellanox systems.
Please CC the i2c-mux maintainer, too.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-18 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 13:49 ` [Re-send: PATCH i2c-next 1/6] i2c: mux: mlxcpld: Update module license Vadim Pasternak
2020-11-18 13:49 ` [Re-send: PATCH i2c-next 2/6] platform/x86: " Vadim Pasternak
2020-11-18 13:49 ` [Re-send: PATCH i2c-next 3/6] i2c: mux: mlxcpld: Move header file out of x86 realm Vadim Pasternak
2020-11-18 13:49 ` [Re-send: PATCH i2c-next 4/6] i2c: mux: mlxcpld: Convert driver to platform driver Vadim Pasternak
2020-11-18 13:49 ` [Re-send: PATCH i2c-next 5/6] i2c: mux: mlxcpld: Extend driver to support word address space devices Vadim Pasternak
2020-11-18 13:49 ` [Re-send: PATCH i2c-next 6/6] i2c: mux: mlxcpld: Extend supported mux number Vadim Pasternak
2020-11-18 14:40 ` Wolfram Sang [this message]
2020-11-18 14:45 ` [Re-send: PATCH i2c-next 0/6] i2c: mux: mlxcpld: Extend driver functionality and update licenses Vadim Pasternak
-- strict thread matches above, loose matches on Subject: below --
2020-11-18 14:44 Vadim Pasternak
2021-01-05 10:27 ` Wolfram Sang
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=20201118144047.GA2649@kunai \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--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).