mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ruipeng Qi <ruipengqi7@gmail.com>,
	catalin.marinas@arm.com, will@kernel.org, bhe@redhat.com,
	vgoyal@redhat.com, dyoung@redhat.com,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Cc: zalbassam@google.com, dianders@chromium.org,
	mark.rutland@arm.com, lecopzer.chen@mediatek.com, maz@kernel.org,
	arnd@arndb.de, yury.norov@gmail.com, brauner@kernel.org,
	mcgrof@kernel.org, maninder1.s@samsung.com,
	michael.christie@oracle.com, samitolvanen@google.com,
	linux-arm-kernel@lists.infradead.org, qiruipeng@lixiang.com
Subject: Re: [PATCH 1/7] [RFC PATCH 1/7] osdump: Add one new os minidump module
Date: Thu, 21 Dec 2023 17:25:08 +0100	[thread overview]
Message-ID: <e9aa311f-6f13-410e-bb35-20320275668c@linaro.org> (raw)
In-Reply-To: <20231221130930.32634-1-ruipengqi7@gmail.com>

On 21/12/2023 14:09, Ruipeng Qi wrote:
> From: qiruipeng <qiruipeng@lixiang.com>
> 
> Osdump is a new crash dumping solution aiming at specific embedded
> devices within automotive or Industrial.
>  - limited memory.
>  - reboot as soon as possible when system fault.

NAK, sorry, work with Qualcomm minidump series to incorporate all your
needs there.

Best regards,
Krzysztof


  reply	other threads:[~2023-12-21 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 13:09 Ruipeng Qi
2023-12-21 16:25 ` Krzysztof Kozlowski [this message]
2023-12-23 14:12   ` ruipeng qi
2023-12-23 14:23     ` Krzysztof Kozlowski
2023-12-23 15:13       ` ruipeng qi
2023-12-23 15:30         ` ruipeng qi
2024-01-08  7:32           ` Mukesh Ojha

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=e9aa311f-6f13-410e-bb35-20320275668c@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bhe@redhat.com \
    --cc=brauner@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dianders@chromium.org \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=lecopzer.chen@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maninder1.s@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=michael.christie@oracle.com \
    --cc=qiruipeng@lixiang.com \
    --cc=ruipengqi7@gmail.com \
    --cc=samitolvanen@google.com \
    --cc=vgoyal@redhat.com \
    --cc=will@kernel.org \
    --cc=yury.norov@gmail.com \
    --cc=zalbassam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®