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, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v3 3/6] mpi3mr: Dump driver and dmesg logs into driver diag buffer
Date: Thu, 30 May 2024 21:04:32 -0400	[thread overview]
Message-ID: <yq1o78meqxy.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240516152010.88227-4-ranjan.kumar@broadcom.com> (Ranjan Kumar's message of "Thu, 16 May 2024 20:50:07 +0530")


Ranjan,

> +	kmsg_dump_rewind(&dumper.kdumper);
> +	while (kmsg_dump_get_line(&dumper.kdumper, 1, NULL, 0, NULL))
> +		n++;
> +
> +	lines = n;
> +	kmsg_dump_rewind(&dumper.kdumper);

Ugh. This is something your userland stuff will have to handle.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2024-05-31  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 15:20 [PATCH v3 0/6] mpi3mr: Host diag buffer support Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 1/6] mpi3mr: HDB allocation and posting for hardware and Firmware buffers Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 2/6] mpi3mr: Driver buffer allocation and posting Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 3/6] mpi3mr: Dump driver and dmesg logs into driver diag buffer Ranjan Kumar
2024-05-31  1:04   ` Martin K. Petersen [this message]
2024-06-05  9:04     ` Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 4/6] mpi3mr: Trigger support Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 5/6] mpi3mr: Ioctl support for HDB Ranjan Kumar
2024-05-16 15:20 ` [PATCH v3 6/6] mpi3mr: Update driver version to 8.9.1.0.50 Ranjan Kumar

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=yq1o78meqxy.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=chandrakanth.patil@broadcom.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@intel.com \
    --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