From: Sudeep Holla <sudeep.holla@arm.com>
To: Scott Branden <scott.branden@broadcom.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Suzuki K Poulose <Suzuki.Poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Steve Capper <steve.capper@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Pramod Kumar <pramod.kumar@broadcom.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Dave Martin <dave.martin@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC 1/1] arm64: Use PSCI calls for CPU stop when hotplug is supported
Date: Wed, 23 Jan 2019 18:07:01 +0000 [thread overview]
Message-ID: <20190123180701.GB1036@e107155-lin> (raw)
In-Reply-To: <90ba929c-362b-a561-1099-5887fc5f6286@broadcom.com>
On Wed, Jan 23, 2019 at 09:46:22AM -0800, Scott Branden wrote:
[...]
>
> Some additional flags and details are saved to disk with the "pending i/o".
>
I am getting a sense that this is some raw partition on a disk(flash/eMMC/UFS)
the M0 can write to and Linux can read. It's can't be full fledge file
system like ext4 were are talking here or are we ?
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-23 18:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 5:46 [PATCH RFC 1/1] arm64: Use PSCI calls for CPU stop when hotplug is supported Pramod Kumar
2019-01-18 11:32 ` Sudeep Holla
[not found] ` <CAJ+tv6+6yqT1xkmkY3x6SNQ83K+J6zqKZr7PV5A_ffvyEzceqg@mail.gmail.com>
2019-01-21 11:22 ` Sudeep Holla
2019-01-23 4:51 ` Pramod Kumar
2019-01-23 16:27 ` Sudeep Holla
[not found] ` <CAJ+tv6KqynSf5t_VwLqpdM4BF+wLWcJ0wPTD4nWqL4ej1Yih4g@mail.gmail.com>
2019-01-21 6:06 ` Pramod Kumar
2019-01-23 16:48 ` Mark Rutland
2019-01-23 17:05 ` Scott Branden
2019-01-23 17:21 ` Sudeep Holla
2019-01-23 17:33 ` Scott Branden
2019-01-23 17:33 ` Mark Rutland
2019-01-23 17:46 ` Scott Branden
2019-01-23 18:07 ` Sudeep Holla [this message]
2019-01-25 7:03 ` Pramod Kumar
2019-01-25 15:56 ` Robin Murphy
2019-01-25 16:52 ` Sudeep Holla
2019-01-23 16:56 ` Mark Rutland
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=20190123180701.GB1036@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=dave.martin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=pramod.kumar@broadcom.com \
--cc=robh@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=steve.capper@arm.com \
--cc=will.deacon@arm.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).