All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	target-devel <target-devel@vger.kernel.org>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Unifying the LIO and SCST target drivers
Date: Thu, 15 Jan 2015 01:08:29 -0800	[thread overview]
Message-ID: <20150115090829.GA14154@infradead.org> (raw)
In-Reply-To: <54B63F74.2040702@sandisk.com>

I don't quite understand whay you're proposing.  We're obbiously not
adding hooks for out of tree code to the kernel.  If you can improve
the target core <-> driver interface (and there's plenty of opportunity
for improvement) and it also happens to help your cause it's all fine

But all that really is a matter of sending patches, and not some out
of the blue discussion.

  parent reply	other threads:[~2015-01-15  9:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 10:05 [LSF/MM TOPIC] Unifying the LIO and SCST target drivers Bart Van Assche
2015-01-14 11:26 ` Hannes Reinecke
2015-01-14 12:23 ` Sagi Grimberg
2015-01-14 23:08 ` Quinn Tran
2015-01-15  0:52 ` Nicholas A. Bellinger
2015-01-15  9:08 ` Christoph Hellwig [this message]
2015-01-15 16:13   ` [Lsf-pc] " Bart Van Assche
2015-01-19  9:21     ` Christoph Hellwig
2015-01-19  9:36       ` Bart Van Assche
2015-02-20 10:49         ` Bart Van Assche
2015-02-21  0:00           ` Nicholas A. Bellinger
2015-02-25  8:43             ` Bart Van Assche
2015-02-27 21:58               ` Nicholas A. Bellinger
2015-02-28 11:59                 ` Bart Van Assche
2015-03-02  6:59                   ` Nicholas A. Bellinger
2015-03-04 10:23                     ` Bart Van Assche
2015-03-05 13:23                       ` Christoph Hellwig
2015-03-05 16:06                         ` Bart Van Assche
2015-03-05 18:38                           ` Andy Grover
2015-03-06  7:25                             ` Bart Van Assche
2015-03-06 19:15                               ` Andy Grover
2015-03-07  2:41                                 ` Sagi Grimberg
2015-03-07  6:25                                 ` Nicholas A. Bellinger
2015-03-09 16:51                                   ` Andy Grover
2015-03-06 23:10                               ` Nicholas A. Bellinger
2015-03-08 16:09                           ` Christoph Hellwig
2015-02-21 20:48           ` Sagi Grimberg
2015-02-22 16:29           ` Christoph Hellwig
2015-03-06 13:36           ` Bart Van Assche
  -- strict thread matches above, loose matches on Subject: below --
2015-02-03 10:06 Dr. Greg Wettstein
2015-02-09 13:16 ` Bart Van Assche
2015-02-12 13:04 Dr. Greg Wettstein
2015-03-06  0:01 Dr. Greg Wettstein

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=20150115090829.GA14154@infradead.org \
    --to=hch@infradead.org \
    --cc=bart.vanassche@sandisk.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=nab@linux-iscsi.org \
    --cc=target-devel@vger.kernel.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 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.