All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Madhani, Himanshu" <Himanshu.Madhani@cavium.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/4] qla2xxx: Add FC-NVMe Target support
Date: Tue, 7 Nov 2017 23:37:36 +0000	[thread overview]
Message-ID: <61AC71F7-4E9F-4B7F-91E6-0B3C3C503DB4@cavium.com> (raw)
In-Reply-To: <20171107150728.GA17161@infradead.org>

Hi Christoph, 

> On Nov 7, 2017, at 7:07 AM, Christoph Hellwig <hch@infradead.org> wrote:
> 
> Please send this to the linux-nvme list, and the nvme FC maintainer.
> 
> Also I'd really like to see Cavium involved with the community a bit
> before we take on another driver.  Right now it's basically just
> James with a bit of help from Johannes.

Sure. I’ll talk to my management about how we can help in the community. 

Thanks,
- Himanshu


      reply	other threads:[~2017-11-07 23:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 19:55 [PATCH 0/4] qla2xxx: Add FC-NVMe Target support Himanshu Madhani
2017-11-06 19:55 ` [PATCH 1/4] qla2xxx_nvmet: Add files for " Himanshu Madhani
2017-11-07 17:05   ` James Smart
2017-11-08 17:35     ` Madhani, Himanshu
2017-11-06 19:55 ` [PATCH 2/4] qla2xxx_nvmet: Added Makefile and Kconfig changes Himanshu Madhani
2017-11-07  8:17   ` kbuild test robot
2017-11-07  8:24   ` kbuild test robot
2017-11-06 19:55 ` [PATCH 3/4] qla2xxx_nvmet: Add FC-NVMe Target LS request handling Himanshu Madhani
2017-11-06 19:55 ` [PATCH 4/4] qla2xxx_nvmet: Add FC-NVMe Target handling Himanshu Madhani
2017-11-07  8:08   ` kbuild test robot
2017-11-07  8:18   ` kbuild test robot
2017-11-13  8:24   ` Dan Carpenter
2017-11-07 15:07 ` [PATCH 0/4] qla2xxx: Add FC-NVMe Target support Christoph Hellwig
2017-11-07 23:37   ` Madhani, Himanshu [this message]

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=61AC71F7-4E9F-4B7F-91E6-0B3C3C503DB4@cavium.com \
    --to=himanshu.madhani@cavium.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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.