public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Doug Ledford <dledford@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-rdma@vger.kernel.org
Subject: Re: CQ and RDMA READ/WRITE APIs
Date: Tue, 17 May 2016 07:38:52 +0200	[thread overview]
Message-ID: <20160517053852.GA25133@lst.de> (raw)
In-Reply-To: <CA+55aFzq+4DJL46B8PXQQG-DpNpzZNzk=O6j+8U_NC6H6BwTdQ@mail.gmail.com>

Hi Linus,

we're not talking about a driver here - we're talking about a new API
lifted from a driver to generic code because it's commonly useful.

It's also in entirely new files and not a modification of existing code,
and it's always been clear how it is.  Some of the code has been in
since Linux 4.5 with a properly clear copyright.

I really don't understand Doug's objection, and as said if they have
a weird problem with it we can simply move it to a separate module.

  parent reply	other threads:[~2016-05-17  5:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <743399f9-10b7-6e62-2bf4-6a8656df8a55@redhat.com>
2016-05-16 11:49 ` CQ and RDMA READ/WRITE APIs Christoph Hellwig
2016-05-16 14:51   ` Doug Ledford
2016-05-16 17:46     ` Linus Torvalds
2016-05-16 18:23       ` Doug Ledford
2016-05-17 17:29         ` Bart Van Assche
2016-05-17 17:32           ` Doug Ledford
2016-05-17 18:50             ` Linus Torvalds
2016-05-18  2:48             ` Parav Pandit
2016-05-18 14:07               ` Doug Ledford
2016-05-18 15:54                 ` Parav Pandit
2016-05-17  5:38       ` Christoph Hellwig [this message]
2016-05-17 15:35         ` Christoph Lameter
2016-05-16 15:26   ` Doug Ledford

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=20160517053852.GA25133@lst.de \
    --to=hch@lst.de \
    --cc=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox