All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Nilesh Javali <njavali@marvell.com>
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	GR-QLogic-Storage-Upstream@marvell.com, agurumurthy@marvell.com,
	sdeodhar@marvell.com
Subject: Re: [PATCH v3 1/9] qla2xxx: Add Unsolicited LS Request and Response Support for NVMe
Date: Thu, 31 Aug 2023 00:44:48 -0700	[thread overview]
Message-ID: <ZPBE8AS+mazj+pBQ@infradead.org> (raw)
In-Reply-To: <20230821130045.34850-2-njavali@marvell.com>

Marting, I saw this made it to linux-next now, please revert it.
qla2xxx hsa absolutely no business changing nvme-fc-driver.h without
ACKs from the NVMe maintainers.


  reply	other threads:[~2023-08-31  7:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 13:00 [PATCH v3 0/9] qla2xxx driver misc features Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 1/9] qla2xxx: Add Unsolicited LS Request and Response Support for NVMe Nilesh Javali
2023-08-31  7:44   ` Christoph Hellwig [this message]
2023-09-13 10:54     ` Christoph Hellwig
2023-09-13 11:03       ` [EXT] " Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 2/9] qla2xxx: Flush mailbox commands on chip reset Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 3/9] qla2xxx: Fix fw resource tracking Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 4/9] qla2xxx: Add logs for SFP temperature monitoring Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 5/9] qla2xxx: Error code did not return to upper layer Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 6/9] qla2xxx: Remove unsupported ql2xenabledif option Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 7/9] qla2xxx: fix smatch warn for qla_init_iocb_limit Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 8/9] Revert "scsi: qla2xxx: Fix buffer overrun" Nilesh Javali
2023-08-21 13:00 ` [PATCH v3 9/9] qla2xxx: Update version to 10.02.09.100-k Nilesh Javali
2023-08-21 22:12 ` [PATCH v3 0/9] qla2xxx driver misc features Martin K. Petersen
2023-08-31  1:48 ` Martin K. Petersen

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=ZPBE8AS+mazj+pBQ@infradead.org \
    --to=hch@infradead.org \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=agurumurthy@marvell.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=njavali@marvell.com \
    --cc=sdeodhar@marvell.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.