public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ranjan Kumar <ranjan.kumar@broadcom.com>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
	rajsekhar.chundru@broadcom.com, sathya.prakash@broadcom.com,
	sumit.saxena@broadcom.com, chandrakanth.patil@broadcom.com,
	prayas.patel@broadcom.com
Subject: Re: [PATCH v6 0/4] mpi3mr: Host diag buffer support
Date: Wed, 26 Jun 2024 23:31:25 -0400	[thread overview]
Message-ID: <yq1msn7f4dz.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240626102646.14298-1-ranjan.kumar@broadcom.com> (Ranjan Kumar's message of "Wed, 26 Jun 2024 15:56:42 +0530")


Ranjan,

> The controllers managed by mpi3mr driver requires system memory to
> save hardware and firmware diagnostic information, this patch set
> enhances the drivers to provide host memory to the controller for
> diagnostic information.  This patch set also provides driver changes
> to push kernel messages into the diagnostic buffers reserved for the
> driver, so that the information will be available as part of debug
> data fetched from the controller.  In addition, support for
> configuring automatic diagnostic information is added in the driver.

Applied to 6.11/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2024-06-27  3:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 10:26 [PATCH v6 0/4] mpi3mr: Host diag buffer support Ranjan Kumar
2024-06-26 10:26 ` [PATCH v6 1/4] mpi3mr: HDB allocation and posting for hardware and Firmware buffers Ranjan Kumar
2024-06-26 10:26 ` [PATCH v6 2/4] mpi3mr: Trigger support Ranjan Kumar
2024-06-26 10:26 ` [PATCH v6 3/4] mpi3mr: ioctl support for HDB Ranjan Kumar
2024-06-26 10:26 ` [PATCH v6 4/4] mpi3mr: Update driver version to 8.9.1.0.50 Ranjan Kumar
2024-06-27  3:31 ` Martin K. Petersen [this message]
2024-07-05  3:53 ` [PATCH v6 0/4] mpi3mr: Host diag buffer support 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=yq1msn7f4dz.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=chandrakanth.patil@broadcom.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=prayas.patel@broadcom.com \
    --cc=rajsekhar.chundru@broadcom.com \
    --cc=ranjan.kumar@broadcom.com \
    --cc=sathya.prakash@broadcom.com \
    --cc=sumit.saxena@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox