linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Khalil Blaiech <kblaiech@nvidia.com>
To: <linux-i2c@vger.kernel.org>
Cc: <kblaiech@nvidia.com>, <wsa+renesas@sang-engineering.com>
Subject: [PATCH i2c-next v1 0/6] i2c: Incremental fixes for Mellanox BlueField I2C
Date: Wed, 28 Oct 2020 18:54:16 -0400	[thread overview]
Message-ID: <cover.1603925077.git.kblaiech@nvidia.com> (raw)

This set of fixes tends to complement the upstream effort of the
driver code and aims to address the following issues:
  - Convert the DT file to a YAML schema to be consistent with the
  latest kernel releases.
  - Fix build issues reproted by the kernel test robot.
  - Apply a couple of changes to the driver code to include bug fixes.
  - Keep the MAINTAINER info up-to-date.

Khalil Blaiech (6):
  i2c: mlxbf: Add CONFIG_ACPI to guard ACPI function call
  i2c: mlxbf: Fix resrticted cast warning of sparse
  i2c: mlxbf: Remove unecessary wrapper functions
  i2c: mlxbf: Update reference clock frequency
  i2c: mlxbf: Update author and maintainer email info
  dt-bindings: i2c: Convert DT file to YAML schema

 .../bindings/i2c/mellanox,i2c-mlxbf.txt       |  42 ----
 .../bindings/i2c/mellanox,i2c-mlxbf.yaml      |  78 +++++++
 MAINTAINERS                                   |   3 +-
 drivers/i2c/busses/i2c-mlxbf.c                | 204 ++++++++----------
 4 files changed, 166 insertions(+), 161 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
 create mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.yaml

-- 
2.24.1


             reply	other threads:[~2020-10-28 22:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 22:54 Khalil Blaiech [this message]
2020-10-28 22:54 ` [PATCH i2c-next v1 1/6] i2c: mlxbf: Add CONFIG_ACPI to guard ACPI function call Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 2/6] i2c: mlxbf: Fix resrticted cast warning of sparse Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 3/6] i2c: mlxbf: Remove unecessary wrapper functions Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 4/6] i2c: mlxbf: Update reference clock frequency Khalil Blaiech
2020-10-28 22:54 ` [PATCH i2c-next v1 5/6] i2c: mlxbf: Update author and maintainer email info Khalil Blaiech
2020-10-28 22:55 ` [PATCH i2c-next v1 6/6] dt-bindings: i2c: Convert DT file to YAML schema Khalil Blaiech
2020-10-29 15:33   ` Rob Herring
2020-11-03 14:08     ` Khalil Blaiech
2020-10-29 15:33   ` Rob Herring
2020-11-03 14:06     ` Khalil Blaiech

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=cover.1603925077.git.kblaiech@nvidia.com \
    --to=kblaiech@nvidia.com \
    --cc=linux-i2c@vger.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;
as well as URLs for NNTP newsgroup(s).