From: Rajan Shanmugavelu <rajan.shanmugavelu@oracle.com>
To: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
srinivas.eeda@oracle.com, joe.jin@oracle.com,
dick.kennedy@broadcom.com, laurie.barry@broadcom.com,
james.smart@broadcom.com
Subject: Gather lpfc debug logs in kernel tracefs ringbuffer
Date: Thu, 16 Jan 2020 09:44:24 -0800 [thread overview]
Message-ID: <1579196665-13504-1-git-send-email-rajan.shanmugavelu@oracle.com> (raw)
Having the lpfc debug logs inside a ring buffer enhances the driver to debug better/faster for hard to reproduce problem saving cyles. Please review.
Thanks,
Rajan
Oracle Linux Engineering.
next reply other threads:[~2020-01-16 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 17:44 Rajan Shanmugavelu [this message]
2020-01-16 17:44 ` [PATCH] lpfc: Gather lpfc debug logs using tracefs ringbuffer Rajan Shanmugavelu
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=1579196665-13504-1-git-send-email-rajan.shanmugavelu@oracle.com \
--to=rajan.shanmugavelu@oracle.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=joe.jin@oracle.com \
--cc=laurie.barry@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=srinivas.eeda@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 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).