linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Allen Hubbe" <Allen.Hubbe@emc.com>
To: "'Serge Semin'" <fancer.lancer@gmail.com>
Cc: <jdmason@kudzu.us>, <dave.jiang@intel.com>,
	<Xiangliang.Yu@amd.com>, <Sergey.Semin@t-platforms.ru>,
	<linux-ntb@googlegroups.com>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 1/3] ntb: Add asynchronous devices support to NTB-bus interface
Date: Fri, 19 Aug 2016 09:41:41 -0400	[thread overview]
Message-ID: <000001d1fa1f$6cddf230$4699d690$@emc.com> (raw)
In-Reply-To: <20160819091000.GA14241@mobilestation>

From: Serge Semin
> 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 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.

I'm sorry to have made you feel that way.

> > I hope we got it settled now. If not, We can have a Skype conversation, since writing
> such a long letters takes lot of time.

Come join irc.oftc.net #ntb

  reply	other threads:[~2016-08-19 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 21:48 [PATCH v2 1/3] ntb: Add asynchronous devices support to NTB-bus interface Allen Hubbe
2016-08-18 21:56 ` Serge Semin
2016-08-19  9:10   ` Serge Semin
2016-08-19 13:41     ` Allen Hubbe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-05 15:31 Allen Hubbe
2016-08-07 17:50 ` Serge Semin
2016-07-26 19:50 [PATCH 0/3] ntb: Asynchronous NTB devices support Serge Semin
2016-07-28 10:01 ` [PATCH v2 " Serge Semin
2016-07-28 10:01   ` [PATCH v2 1/3] ntb: Add asynchronous devices support to NTB-bus interface Serge Semin

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='000001d1fa1f$6cddf230$4699d690$@emc.com' \
    --to=allen.hubbe@emc.com \
    --cc=Sergey.Semin@t-platforms.ru \
    --cc=Xiangliang.Yu@amd.com \
    --cc=dave.jiang@intel.com \
    --cc=fancer.lancer@gmail.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntb@googlegroups.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).