From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Tariq Toukan <tariqt@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Gal Pressman <gal@nvidia.com>
Subject: Re: [PATCH net-next] MAINTAINERS: Update Mellanox website links
Date: Sun, 21 Apr 2024 08:19:24 -0700 [thread overview]
Message-ID: <87sezeaghq.fsf@nvidia.com> (raw)
In-Reply-To: <20240421145414.GF6832@unreal>
On Sun, 21 Apr, 2024 17:54:14 +0300 Leon Romanovsky <leon@kernel.org> wrote:
> On Sun, Apr 21, 2024 at 05:39:14PM +0300, Tariq Toukan wrote:
>> From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
>>
>> Old mellanox.com domain is no longer functional.
>
> It is not true, the domain is still functional and www.mellanox.com
> redirects to https://www.nvidia.com/en-us/networking/.
I am not sure I consider redirecting to another site to be functional
but will update the wording. Not sure how long that redirect will last.
>
> Or change all links to point to that redirect or leave old links as is.
> And I'm not sure that this patch makes any difference for mlx4.
I am opting to use the link below so it will pick the
language/geographical endpoint correctly.
https://www.nvidia.com/networking/
--
Thanks,
Rahul Rameshbabu
next prev parent reply other threads:[~2024-04-21 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 14:39 [PATCH net-next] MAINTAINERS: Update Mellanox website links Tariq Toukan
2024-04-21 14:54 ` Leon Romanovsky
2024-04-21 15:19 ` Rahul Rameshbabu [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-05 5:22 Tariq Toukan
2024-08-06 20:28 ` patchwork-bot+netdevbpf
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=87sezeaghq.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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.