From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Khalil Blaiech <kblaiech@nvidia.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Khalil Blaiech <kblaiech@mellanox.com>,
Vadim Pasternak <vadimp@mellanox.com>
Subject: Re: [PATCH v11 1/2] i2c: i2c-mlxbf: I2C SMBus driver for Mellanox BlueField SoC
Date: Wed, 30 Sep 2020 07:41:52 +0200 [thread overview]
Message-ID: <20200930054152.GA1305@ninjato> (raw)
In-Reply-To: <MN2PR12MB36160C5BC782D9AF3A017D17AB320@MN2PR12MB3616.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
On Tue, Sep 29, 2020 at 10:45:56PM +0000, Khalil Blaiech wrote:
> 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.
You are welcome. But please don't send new versions anymore now but only
incremental patches which go on top of v11. That is the normal
procedure. Thank you as well!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-30 5:41 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
2020-09-30 5:41 ` Wolfram Sang [this message]
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
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=20200930054152.GA1305@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=kblaiech@mellanox.com \
--cc=kblaiech@nvidia.com \
--cc=linux-i2c@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).