From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Salomon Dushimirimana <salomondush@google.com>
Cc: Jinpu Wang <jinpu.wang@ionos.com>,
Jack Wang <jinpu.wang@cloud.ionos.com>,
"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Bhavesh Jashnani <bjashnani@google.com>
Subject: Re: [PATCH] scsi: pm80xx: Use module param to set pcs event log severity
Date: Fri, 25 Oct 2024 14:45:36 -0400 [thread overview]
Message-ID: <yq1frokf2ii.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CAPE3x15ryZw4s=qA=7HSDyZZXf3FUz2Ms7cxXHjc_R+UbPZTwA@mail.gmail.com> (Salomon Dushimirimana's message of "Thu, 17 Oct 2024 12:58:10 -0400")
Salomon,
> 3 works well for Google, but a different value might be better for
> others. Having a module parameter would allow users to customize the
> level of logging based on their specific needs. If that is not a
> concern, I can change the default to just 3.
How verbose will a value of 3 be during normal operation? I don't object
to capturing more information during failure scenarios as long as we're
not flooding the logs with noise when things are nominal.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-10-25 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 22:09 [PATCH] scsi: pm80xx: Use module param to set pcs event log severity Salomon Dushimirimana
2024-10-17 6:45 ` Jinpu Wang
2024-10-17 16:58 ` Salomon Dushimirimana
2024-10-25 18:45 ` Martin K. Petersen [this message]
2024-10-28 23:57 ` Salomon Dushimirimana
2024-11-03 0:15 ` Martin K. Petersen
2024-11-14 2:50 ` 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=yq1frokf2ii.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bjashnani@google.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=jinpu.wang@ionos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=salomondush@google.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.