All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Khalil Blaiech <kblaiech@nvidia.com>
Cc: Rob Herring <robh@kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	Khalil Blaiech <kblaiech@mellanox.com>,
	Vadim Pasternak <vadimp@mellanox.com>
Subject: Re: [PATCH v11 2/2] dt-bindings: i2c: I2C binding for Mellanox BlueField SoC
Date: Wed, 30 Sep 2020 07:44:07 +0200	[thread overview]
Message-ID: <20200930054407.GB1305@ninjato> (raw)
In-Reply-To: <MN2PR12MB361651014BE6D69C6792A805AB320@MN2PR12MB3616.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]


> Our driver supports both ACPI and devicetree. However, the platform
> firmware running on our platform implements ACPI and doesn't
> really rely on devicetree. Do you think we should keep the devicetree
> support? Or should I get rid of it before we apply the patch?

Usually, I'd say, if it is not used, remove it. If it would be used in
the near future, then we could keep it. But that you know better than I
do :)


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-09-30  5:44 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
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 [this message]

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=20200930054407.GB1305@ninjato \
    --to=wsa@kernel.org \
    --cc=kblaiech@mellanox.com \
    --cc=kblaiech@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=robh@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 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.