All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khalil Blaiech <kblaiech@nvidia.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.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: Mon, 5 Oct 2020 23:54:18 +0000	[thread overview]
Message-ID: <MN2PR12MB36167849F16529392C0337D1AB0C0@MN2PR12MB3616.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200930054152.GA1305@ninjato>


> > 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!

Thank you.

Please note that I addressed the build issue and converted the DT file
into YAML schema.
Please allow some time for the internal review,  I will post the patches
to the Linux kernel afterwards. 

  reply	other threads:[~2020-10-05 23:54 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
2020-10-05 23:54         ` Khalil Blaiech [this message]
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=MN2PR12MB36167849F16529392C0337D1AB0C0@MN2PR12MB3616.namprd12.prod.outlook.com \
    --to=kblaiech@nvidia.com \
    --cc=kblaiech@mellanox.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=vadimp@mellanox.com \
    --cc=wsa+renesas@sang-engineering.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.