From: Asmaa Mnebhi <asmaa@nvidia.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
robh@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: Asmaa Mnebhi <asmaa@nvidia.com>
Subject: [PATCH v7 0/2] i2c: i2c-mlxbf.c: bug fixes and new feature support
Date: Tue, 27 Sep 2022 16:39:22 -0400 [thread overview]
Message-ID: <20220927203924.22644-1-asmaa@nvidia.com> (raw)
Support BlueField-3 SoC in the first patch of this series and remove
the device tree support in the second patch.
What has changed from v6->v7:
- the following patches were applied to for-next so they are removed
from this series:
1) Support lock mechanism to avoid race condition between entities
using the i2c bus
2) remove IRQF_ONESHOT flag as it is no longer needed.
3) Support multi slave functionality
- Fixed the $subject tag to "i2c: mlxbf"
- added missing check for 'ret' after allocating resources
- removed the DT binding file from the MAINTAINERS file
Asmaa Mnebhi (2):
i2c: mlxbf: support BlueField-3 SoC
i2c: mlxbf: remove device tree support
.../bindings/i2c/mellanox,i2c-mlxbf.yaml | 77 ---
MAINTAINERS | 2 +-
drivers/i2c/busses/i2c-mlxbf.c | 494 ++++++++++--------
3 files changed, 281 insertions(+), 292 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.yaml
--
2.30.1
next reply other threads:[~2022-09-27 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 20:39 Asmaa Mnebhi [this message]
2022-09-27 20:39 ` [PATCH v7 1/2] i2c: mlxbf: support BlueField-3 SoC Asmaa Mnebhi
2022-09-27 20:46 ` Wolfram Sang
2022-09-27 21:00 ` Asmaa Mnebhi
2022-09-27 20:39 ` [PATCH v7 2/2] i2c: mlxbf: remove device tree support Asmaa Mnebhi
2022-09-27 20:46 ` 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=20220927203924.22644-1-asmaa@nvidia.com \
--to=asmaa@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox