From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Khalil Blaiech <kblaiech@mellanox.com>,
Vadim Pasternak <vadimp@mellanox.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: mlxbf: I2C_MLXBF should depend on MELLANOX_PLATFORM
Date: Fri, 6 Nov 2020 15:58:09 +0100 [thread overview]
Message-ID: <20201106145809.GH1059@kunai> (raw)
In-Reply-To: <20201010111942.GF4669@ninjato>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Sat, Oct 10, 2020 at 01:19:42PM +0200, Wolfram Sang wrote:
> On Mon, Oct 05, 2020 at 02:49:49PM +0200, Geert Uytterhoeven wrote:
> > The Mellanox BlueField I2C controller is only present on Mellanox
> > BlueField SoCs. Hence add a dependency on MELLANOX_PLATFORM, to prevent
> > asking the user about this driver when configuring a kernel without
> > Mellanox platform support.
> >
> > Fixes: b5b5b32081cd206b ("i2c: mlxbf: I2C SMBus driver for Mellanox BlueField SoC")
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Usually, I wait for maintainer acks before I apply driver patches. I
> make an exception here to have it sorted out before the merge window.
>
> Applied to for-next, thanks!
Strange, this one got missing, too. Applied again to for-current!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-11-06 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 12:49 [PATCH] i2c: mlxbf: I2C_MLXBF should depend on MELLANOX_PLATFORM Geert Uytterhoeven
2020-10-10 11:19 ` Wolfram Sang
2020-11-06 14:58 ` 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=20201106145809.GH1059@kunai \
--to=wsa+renesas@sang-engineering.com \
--cc=geert+renesas@glider.be \
--cc=kblaiech@mellanox.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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).