linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Ranjan Kumar <ranjan.kumar@broadcom.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Subject: Re: [PATCH] mpt3sas: Remove logging BIOS version in the kernel log
Date: Sun, 02 Apr 2023 21:07:26 -0400	[thread overview]
Message-ID: <yq1lej9ydw3.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CAFdVvOzP5v6LO5RbK+=7gPmOX_Lv5MO1viWMUCbusNcc3pe=GA@mail.gmail.com> (Sathya Prakash Veerichetty's message of "Mon, 27 Mar 2023 10:57:22 -0600")


Sathya,

> The only proper way to print UEFI Boot Services Driver version and
> legacy x86 OpROM version is to upload those image headers from flash
> and retrieve the version, various generation of the controllers have
> various type of image headers hence a good amount of code needs to be
> added to the driver to display them properly and associated feature
> maintenance, so we thought it is better to push that to applications
> space

OK. As long as the firmware version is printed, I guess we can live
without the legacy BIOS.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2023-04-03  1:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  9:27 [PATCH] mpt3sas: Remove logging BIOS version in the kernel log Ranjan Kumar
2023-03-25  0:51 ` Martin K. Petersen
2023-03-27 16:57   ` Sathya Prakash Veerichetty
2023-04-03  1:07     ` Martin K. Petersen [this message]
2023-04-19  3:20 ` 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=yq1lej9ydw3.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ranjan.kumar@broadcom.com \
    --cc=sathya.prakash@broadcom.com \
    --cc=sreekanth.reddy@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;
as well as URLs for NNTP newsgroup(s).