All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Thompson <davthompson@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Liming Sun <limings@nvidia.com>, Asmaa Mnebhi <asmaa@nvidia.com>
Subject: RE: [PATCH net-next v5] Add Mellanox BlueField Gigabit Ethernet driver
Date: Tue, 1 Jun 2021 01:10:36 +0000	[thread overview]
Message-ID: <BN9PR12MB5340F9DC21DA0F1634279F82C73E9@BN9PR12MB5340.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210528151442.470bbca7@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>

> -----Original Message-----
> From: Jakub Kicinski <kuba@kernel.org>
> Sent: Friday, May 28, 2021 6:15 PM
> To: David Thompson <davthompson@nvidia.com>
> Cc: davem@davemloft.net; netdev@vger.kernel.org; Liming Sun
> <limings@nvidia.com>; Asmaa Mnebhi <asmaa@nvidia.com>
> Subject: Re: [PATCH net-next v5] Add Mellanox BlueField Gigabit Ethernet driver
> 
> On Fri, 28 May 2021 15:37:19 -0400 David Thompson wrote:
> > This patch adds build and driver logic for the "mlxbf_gige"
> > Ethernet driver from Mellanox Technologies. The second generation
> > BlueField SoC from Mellanox supports an out-of-band GigaBit Ethernet
> > management port to the Arm subsystem.  This driver supports TCP/IP
> > network connectivity for that port, and provides back-end routines to
> > handle basic ethtool requests.
> 
> Please address the 32 bit build warnings.

My apologies Jakub.  Prior versions of this patch did compile for ARM32.

I will change the code accordingly so that ARM32 build succeeds.

Regards, Dave

  reply	other threads:[~2021-06-01  1:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 19:37 [PATCH net-next v5] Add Mellanox BlueField Gigabit Ethernet driver David Thompson
2021-05-28 22:14 ` Jakub Kicinski
2021-06-01  1:10   ` David Thompson [this message]
2021-05-29  0:22 ` Andrew Lunn
2021-06-01 12:48   ` Asmaa Mnebhi
2021-06-01 13:19     ` Andrew Lunn
2021-06-01 13:43       ` Asmaa Mnebhi
2021-06-01 14:12         ` Andrew Lunn

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=BN9PR12MB5340F9DC21DA0F1634279F82C73E9@BN9PR12MB5340.namprd12.prod.outlook.com \
    --to=davthompson@nvidia.com \
    --cc=asmaa@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=limings@nvidia.com \
    --cc=netdev@vger.kernel.org \
    /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.