From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: lsf-pc <lsf-pc@lists.linux-foundation.org>,
"Roland Dreier" <roland@kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
"Hannes Reinecke" <mail@hannes-reinecke.de>,
"Madhu Iyengar" <madhu.iyengar@qlogic.com>,
target-devel <target-devel@vger.kernel.org>,
"Andrew Vasquez" <andrew.vasquez@qlogic.com>,
"Christoph Hellwig" <hch@lst.de>, "Jörn Engel" <joern@logfs.org>,
"Arun Easi" <arun.easi@qlogic.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] [ATTEND] qla2xxx FC target mode
Date: Mon, 19 Mar 2012 08:54:19 +0000 [thread overview]
Message-ID: <1332147259.3152.3.camel@dabdike> (raw)
In-Reply-To: <1332116541.1612.118.camel@haakon2.linux-iscsi.org>
On Sun, 2012-03-18 at 17:22 -0700, Nicholas A. Bellinger wrote:
> On Sun, 2012-03-18 at 09:22 +0000, James Bottomley wrote:
> > On Fri, 2012-03-16 at 16:40 -0700, Nicholas A. Bellinger wrote:
> > > James & Co,
> > >
> > > Ping..? Any thoughts on this topic yet..?
> >
> > Not really ... we're trying to get the participants to plan the topics
> > this year.
> >
>
> Hi James,
>
> I'm asking because the invites for an LSF slot this year to discuss this
> topic with the development community has not materialized, and you've
> been completely silent to qla2xxx target RFCs + patches that involve the
> subject thus far..
It's not my driver, it's qlogic's ... I'm not really going to say
anything until they do.
James
next prev parent reply other threads:[~2012-03-19 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 0:27 [LSF/MM TOPIC] [ATTEND] qla2xxx FC target mode Nicholas A. Bellinger
2012-03-16 23:40 ` Nicholas A. Bellinger
2012-03-18 9:22 ` [Lsf-pc] " James Bottomley
2012-03-19 0:22 ` Nicholas A. Bellinger
2012-03-19 8:54 ` James Bottomley [this message]
2012-03-20 0:15 ` Nicholas A. Bellinger
2012-03-20 9:03 ` James Bottomley
2012-03-21 4:12 ` Nicholas A. Bellinger
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=1332147259.3152.3.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=andrew.vasquez@qlogic.com \
--cc=arun.easi@qlogic.com \
--cc=hch@lst.de \
--cc=joern@logfs.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=madhu.iyengar@qlogic.com \
--cc=mail@hannes-reinecke.de \
--cc=nab@linux-iscsi.org \
--cc=roland@kernel.org \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).