From: Khalil Blaiech <firstname.lastname@example.org>
To: Wolfram Sang <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>,
Khalil Blaiech <firstname.lastname@example.org>,
Vadim Pasternak <email@example.com>
Subject: RE: [PATCH v11 1/2] i2c: i2c-mlxbf: I2C SMBus driver for Mellanox BlueField SoC
Date: Tue, 29 Sep 2020 22:45:56 +0000 [thread overview]
Message-ID: <MN2PR12MB36160C5BC782D9AF3A017D17AB320@MN2PR12MB3616.namprd12.prod.outlook.com> (raw)
Wolfram, thank you very much.
I have seen that you applied it to "for-next" branch.
I 'll address the build issue as soon as possible and post a v12
with the appropriate tags.
> -----Original Message-----
> From: Wolfram Sang <firstname.lastname@example.org>
> Sent: Sunday, September 27, 2020 9:55 AM
> To: Khalil Blaiech <email@example.com>
> Cc: firstname.lastname@example.org; Khalil Blaiech <email@example.com>;
> Vadim Pasternak <firstname.lastname@example.org>
> Subject: Re: [PATCH v11 1/2] i2c: i2c-mlxbf: I2C SMBus driver for Mellanox
> BlueField SoC
> On Tue, Sep 22, 2020 at 06:49:37PM -0400, Khalil Blaiech wrote:
> > From: Khalil Blaiech <email@example.com>
> > Add BlueField I2C driver to offer master and slave support for
> > Mellanox BlueField SoCs. The driver implements an SMBus adapter
> > and interfaces to multiple busses that can be probed using both
> > ACPI and Device Tree infrastructures.
> > The driver supports several SMBus operations to transfer data
> > back and forth from/to various I2C devices. It is mainly intended
> > to be consumed by userspace tools and utilities, such as i2c-tools
> > and decode-dimms to collect memory module information.
> > On the other hand, the driver has a slave function to support,
> > among others, an IPMB interface that requires both master and
> > slave functions to handle transfers between the BlueField SoC
> > and a board management controllers (e.g., BMC).
> > Signed-off-by: Khalil Blaiech <firstname.lastname@example.org>
> > Reviewed-by: Vadim Pasternak <email@example.com>
> Applied to for-next, thanks!
next prev parent reply other threads:[~2020-09-29 22:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 22:49 [PATCH v11 0/2] i2c: add driver for Mellanox BlueField SoC Khalil Blaiech
2020-09-22 22:49 ` [PATCH v11 1/2] i2c: i2c-mlxbf: I2C SMBus " Khalil Blaiech
2020-09-27 13:54 ` Wolfram Sang
2020-09-29 22:45 ` Khalil Blaiech [this message]
2020-09-30 5:41 ` Wolfram Sang
2020-10-05 23:54 ` Khalil Blaiech
2020-10-22 14:45 ` Khalil Blaiech
2020-09-22 22:49 ` [PATCH v11 2/2] dt-bindings: i2c: I2C binding " Khalil Blaiech
2020-09-22 23:05 ` Rob Herring
2020-09-29 22:59 ` Khalil Blaiech
2020-09-27 13:57 ` Wolfram Sang
2020-09-29 22:58 ` Khalil Blaiech
2020-09-30 5:44 ` Wolfram Sang
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.