diff for duplicates of <20160819091000.GA14241@mobilestation> diff --git a/a/1.txt b/N1/1.txt index 8f5c9e8..7486f06 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -89,7 +89,7 @@ ntb_msg_send(ntb, idx, msg, target_port); - send a message to the corresponding 3) IDT driver redevelopment will take a lot of time, since I don't have much free time to do it. It may be half of year or even more. -From my side, such an improvement will significantly complicate the NTB Kernel API. Since you +>From my side, such an improvement will significantly complicate the NTB Kernel API. Since you are the subsystem maintainer it's your decision which design to choose, but I don't think I'll do the IDT driver suitable for this design anytime soon. @@ -131,7 +131,7 @@ On Fri, Aug 19, 2016 at 12:56:04AM +0300, Serge Semin <fancer.lancer@gmail.com> > > > 1) Two NTB-ported switches (models 89PES8NT2, 89PES16NT2, 89PES12NT3, 89PES124NT3), > > > 2) Multi NTB-ported switches (models 89HPES24NT6AG2, 89HPES32NT8AG2, 89HPES32NT8BG2, > > > 89HPES12NT12G2, 89HPES16NT16G2, 89HPES24NT24G2, 89HPES32NT24AG2, 89HPES32NT24BG2). -> > > Just to note all of these switches are a part of IDT PRECISE(TM) family of PCI Express� +> > > Just to note all of these switches are a part of IDT PRECISE(TM) family of PCI Express® > > > switching solutions. Why do I split them up? Because of the next reasons: > > > 1) Number of upstream ports, which have access to NTB functions (obviously, yeah? =)). So > > > the switches of the first group can connect just two domains over NTB. Unlike the second diff --git a/a/content_digest b/N1/content_digest index a47675b..c71d338 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -103,7 +103,7 @@ "3) IDT driver redevelopment will take a lot of time, since I don't have much free time to do\n" "it. It may be half of year or even more.\n" "\n" - "From my side, such an improvement will significantly complicate the NTB Kernel API. Since you\n" + ">From my side, such an improvement will significantly complicate the NTB Kernel API. Since you\n" "are the subsystem maintainer it's your decision which design to choose, but I don't think I'll do\n" "the IDT driver suitable for this design anytime soon.\n" "\n" @@ -145,7 +145,7 @@ "> > > 1) Two NTB-ported switches (models 89PES8NT2, 89PES16NT2, 89PES12NT3, 89PES124NT3),\n" "> > > 2) Multi NTB-ported switches (models 89HPES24NT6AG2, 89HPES32NT8AG2, 89HPES32NT8BG2,\n" "> > > 89HPES12NT12G2, 89HPES16NT16G2, 89HPES24NT24G2, 89HPES32NT24AG2, 89HPES32NT24BG2).\n" - "> > > Just to note all of these switches are a part of IDT PRECISE(TM) family of PCI Express\303\257\302\277\302\275\n" + "> > > Just to note all of these switches are a part of IDT PRECISE(TM) family of PCI Express\302\256\n" "> > > switching solutions. Why do I split them up? Because of the next reasons:\n" "> > > 1) Number of upstream ports, which have access to NTB functions (obviously, yeah? =)). So\n" "> > > the switches of the first group can connect just two domains over NTB. Unlike the second\n" @@ -940,4 +940,4 @@ "> > \n" > > -f79099dd25e7c295662b2460c5b4730527df7e22d51a9a8a4b4951bf4d51ab29 +f56644c64534dc4fa38cd43fb686a75ca04b8c23163147887e0fc84c899f112e
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.