From: Aviad Krawczyk <aviad.krawczyk@huawei.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: David Miller <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Networking <netdev@vger.kernel.org>, <bc.y@huawei.com>,
<victor.gissin@huawei.com>, <zhaochen6@huawei.com>,
<tony.qu@huawei.com>
Subject: Re: [PATCH V8 net-next 00/22] Huawei HiNIC Ethernet Driver
Date: Wed, 23 Aug 2017 13:46:24 +0300 [thread overview]
Message-ID: <f0b00e85-3cc0-1b80-94d4-41c7ab58dc15@huawei.com> (raw)
In-Reply-To: <CAK8P3a0St2mZ7q33zccHZ1uPyv0FKf2A+q+cMk+LN_L_qjxfkg@mail.gmail.com>
Hi,
> It's clear that ...
Sorry, but there are wrong assumptions here.
Thanks,
Aviad
On 8/23/2017 1:37 PM, Arnd Bergmann wrote:
> On Wed, Aug 23, 2017 at 11:31 AM, Aviad Krawczyk
> <aviad.krawczyk@huawei.com> wrote:
>> Hi Arnd,
>>
>> This is Huawei's PCIE HiNIC card.
>>
>> I am not familiar with the HiSilicon product and I don't see how
>> Huawei's PCIE HiNIC card is connected to the HiSilicon drivers on Linux Tree.
>>
>> I don't see how it can be shared: different product and different code.
>
> Sharing code was just a wild thought of mine, as I said I had not looked at
> whether there is anything that can be shared.
>
> However, simply moving drivers/net/ethernet/huawei/hinic to
> drivers/net/ethernet/hisilicon/hinic/ still seems to be the right thing and
> is a trivial patch.
>
> It's clear that hinic is made by HiSilicon and that hns/hns3 are used
> exclusively in Huawei, and maintained by Huawei developers, so it's
> probably just a matter of time before the IP block from the SoC makes
> it into a future PCI device or vice versa. Merging the two directories
> now makes this easier to handle in the future and (slightly) reduces
> the clutter in the top-level drivers/net/ethernet/Kconfig file.
>
> Arnd
>
> .
>
prev parent reply other threads:[~2017-08-23 10:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 15:55 Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 01/22] net-next/hinic: Initialize hw interface Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 02/22] net-next/hinic: Initialize hw device components Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 03/22] net-next/hinic: Initialize api cmd resources Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 04/22] net-next/hinic: Initialize api cmd hw Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 05/22] net-next/hinic: Add management messages Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 06/22] net-next/hinic: Add api cmd commands Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 07/22] net-next/hinic: Add aeqs Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 08/22] net-next/hinic: Add port management commands Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 09/22] net-next/hinic: Add Rx mode and link event handler Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 10/22] net-next/hinic: Add logical Txq and Rxq Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 11/22] net-next/hinic: Add wq Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 12/22] net-next/hinic: Add qp resources Aviad Krawczyk
2017-08-21 15:55 ` [PATCH V8 net-next 13/22] net-next/hinic: Set qp context Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 14/22] net-next/hinic: Initialize cmdq Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 15/22] net-next/hinic: Add ceqs Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 16/22] net-next/hinic: Add cmdq commands Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 17/22] net-next/hinic: Add cmdq completion handler Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 18/22] net-next/hinic: Add Rx handler Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 19/22] net-next/hinic: Add Tx operation Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 20/22] net-next/hinic: Add ethtool and stats Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 21/22] net-next/hinic: Add netpoll Aviad Krawczyk
2017-08-21 15:56 ` [PATCH V8 net-next 22/22] net-next/hinic: Add Maintainer Aviad Krawczyk
2017-08-22 17:58 ` [PATCH V8 net-next 00/22] Huawei HiNIC Ethernet Driver David Miller
2017-08-23 9:14 ` Aviad Krawczyk
2017-08-23 7:37 ` Arnd Bergmann
2017-08-23 9:31 ` Aviad Krawczyk
2017-08-23 10:37 ` Arnd Bergmann
2017-08-23 10:46 ` Aviad Krawczyk [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=f0b00e85-3cc0-1b80-94d4-41c7ab58dc15@huawei.com \
--to=aviad.krawczyk@huawei.com \
--cc=arnd@arndb.de \
--cc=bc.y@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tony.qu@huawei.com \
--cc=victor.gissin@huawei.com \
--cc=zhaochen6@huawei.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
all inboxes | Powered by JetHome®