From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Shravan Kumar Ramani <sramani@mellanox.com>
Cc: Andy Shevchenko <andy@infradead.org>,
Darren Hart <dvhart@infradead.org>,
Vadim Pasternak <vadimp@mellanox.com>,
Liming Sun <lsun@mellanox.com>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] platform/mellanox: Add Mellanox TRIO driver
Date: Mon, 18 Nov 2019 12:47:11 +0200 [thread overview]
Message-ID: <CAHp75VdWM8Y7TAbVYNoo9vV2N+ZYDZWWGHtgvt8WjD5KiFfZRA@mail.gmail.com> (raw)
In-Reply-To: <cover.1573460910.git.sramani@mellanox.com>
On Mon, Nov 11, 2019 at 4:35 PM Shravan Kumar Ramani
<sramani@mellanox.com> wrote:
>
> This patch adds support for Mellanox BlueField TRIO PCIe host controller.
> The driver supports multiple TRIO instances and provides a sysfs interface
> to allow the user to read/set the L3 cache profile for transactions going
> through the TRIO. It also provides an interrupt handler for the TRIO blocks.
Besides on-going review, this doesn't apply. So, please check that you
rebase it on top of our for-next branch, thanks!
P.S. I'll wait for v2 with Vadim's comments being addressed.
>
> Shravan Kumar Ramani (1):
> platform/mellanox: Add Mellanox TRIO driver
>
> MAINTAINERS | 5 +
> drivers/platform/mellanox/Kconfig | 8 +
> drivers/platform/mellanox/Makefile | 1 +
> drivers/platform/mellanox/mlxbf-trio.c | 624 +++++++++++++++++++++++++++++++++
> 4 files changed, 638 insertions(+)
> create mode 100644 drivers/platform/mellanox/mlxbf-trio.c
>
> --
> 2.1.2
>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2019-11-18 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 14:34 [PATCH v1] platform/mellanox: Add Mellanox TRIO driver Shravan Kumar Ramani
2019-11-11 14:34 ` Shravan Kumar Ramani
2019-11-12 14:44 ` Vadim Pasternak
2019-11-13 5:40 ` Shravan Ramani
2019-11-13 7:05 ` Vadim Pasternak
2019-11-18 10:47 ` Andy Shevchenko [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=CAHp75VdWM8Y7TAbVYNoo9vV2N+ZYDZWWGHtgvt8WjD5KiFfZRA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsun@mellanox.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sramani@mellanox.com \
--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).