All of lore.kernel.org
 help / color / mirror / Atom feed
From: James.Bottomley@HansenPartnership.com (James Bottomley)
Subject: [Lsf-pc] [LSF/MM TOPIC] NVMe target support
Date: Thu, 28 Jan 2016 07:25:25 -0800	[thread overview]
Message-ID: <1453994725.2342.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <56AA30C6.10806@sandisk.com>

On Thu, 2016-01-28@07:16 -0800, Bart Van Assche wrote:
> On 01/27/16 20:41, Nicholas A. Bellinger wrote:
> > [ ... ]
> > The folks for such a discussion would include:
> > 
> >     Christoph Hellwig, Hannes Reinecke, Dave Minturn, Sagi
> > Grimberg,
> >     Ming Lin, Roland Dreier and Mike Christie.
> 
> Hello Nic,
> 
> Since the LSF/MM summit is organized by the Linux Foundation

This is a misperception.  LSF/MM is organised by a group of volunteers
as a Linux Kernel mini summit to discuss current topics around those
subsystems.

>  and since one of the goals of the Linux Foundation is to promote
> Linux I think every company that is active in both the NVMeOF
> committee and in the Linux kernel community should be invited.

  We use the LF to do the logistics, but it's in no way controlled by
them or aligned with their member companies.  The first LSF/MM was
aided logistically by google, the next by Intel, then USENIX for a
while and now the LF.

I certainly wouldn't be in favour of turning LSF/MM into a corporate
discussion forum ... that's what standards bodies are for.

James

>  That includes but is not limited to companies like Oracle, Micron,
> EMC, NetApp, HGST and also my own employer SanDisk (see e.g. 
> http://www.nvmexpress.org/).
> 
> Thanks,
> 
> Bart.
> _______________________________________________
> Lsf-pc mailing list
> Lsf-pc at lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lsf-pc
> 

WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	lsf-pc <lsf-pc@lists.linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	target-devel <target-devel@vger.kernel.org>,
	linux-nvme@lists.infradead.org
Cc: "Minturn, Dave B" <dave.b.minturn@intel.com>,
	Roland Dreier <roland@kernel.org>,
	Sagi Grimberg <sagig@mellanox.com>,
	Mike Christie <mchristi@redhat.com>,
	Hannes Reinecke <hare@suse.de>, Ming Lin <mlin@kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] NVMe target support
Date: Thu, 28 Jan 2016 07:25:25 -0800	[thread overview]
Message-ID: <1453994725.2342.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <56AA30C6.10806@sandisk.com>

On Thu, 2016-01-28 at 07:16 -0800, Bart Van Assche wrote:
> On 01/27/16 20:41, Nicholas A. Bellinger wrote:
> > [ ... ]
> > The folks for such a discussion would include:
> > 
> >     Christoph Hellwig, Hannes Reinecke, Dave Minturn, Sagi
> > Grimberg,
> >     Ming Lin, Roland Dreier and Mike Christie.
> 
> Hello Nic,
> 
> Since the LSF/MM summit is organized by the Linux Foundation

This is a misperception.  LSF/MM is organised by a group of volunteers
as a Linux Kernel mini summit to discuss current topics around those
subsystems.

>  and since one of the goals of the Linux Foundation is to promote
> Linux I think every company that is active in both the NVMeOF
> committee and in the Linux kernel community should be invited.

  We use the LF to do the logistics, but it's in no way controlled by
them or aligned with their member companies.  The first LSF/MM was
aided logistically by google, the next by Intel, then USENIX for a
while and now the LF.

I certainly wouldn't be in favour of turning LSF/MM into a corporate
discussion forum ... that's what standards bodies are for.

James

>  That includes but is not limited to companies like Oracle, Micron,
> EMC, NetApp, HGST and also my own employer SanDisk (see e.g. 
> http://www.nvmexpress.org/).
> 
> Thanks,
> 
> Bart.
> _______________________________________________
> Lsf-pc mailing list
> Lsf-pc@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lsf-pc
> 

  reply	other threads:[~2016-01-28 15:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  4:41 [LSF/MM TOPIC] NVMe target support Nicholas A. Bellinger
2016-01-28  4:41 ` Nicholas A. Bellinger
2016-01-28  8:52 ` Christoph Hellwig
2016-01-28  8:52   ` Christoph Hellwig
2016-01-28  9:09   ` Nicholas A. Bellinger
2016-01-28  9:09     ` Nicholas A. Bellinger
2016-01-28  9:11     ` Christoph Hellwig
2016-01-28  9:11       ` Christoph Hellwig
2016-01-28  9:17       ` Judy Brock-SSI
2016-01-28  9:17         ` Judy Brock-SSI
2016-01-28  9:19       ` Nicholas A. Bellinger
2016-01-28  9:19         ` Nicholas A. Bellinger
2016-01-28 15:16 ` Bart Van Assche
2016-01-28 15:16   ` Bart Van Assche
2016-01-28 15:25   ` James Bottomley [this message]
2016-01-28 15:25     ` [Lsf-pc] " James Bottomley

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=1453994725.2342.5.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.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 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.