From: Markus Elfring <Markus.Elfring@web.de>
To: Kah Jing Lee <kah.jing.lee@intel.com>,
Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@intel.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Conor Dooley <conor+dt@kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Will Deacon <will@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, "cocci@inria.fr" <cocci@inria.fr>
Subject: Re: [cocci] [v2 1/2] arm64: dts: agilex/stratix10: Updated QSPI Flash layout for UBIFS
Date: Fri, 23 Jun 2023 13:03:55 +0200 [thread overview]
Message-ID: <c15e650e-6aee-d3e1-3fe1-7e5d34813a04@web.de> (raw)
In-Reply-To: <PH0PR11MB56730E97D182D413C9B555E1CB23A@PH0PR11MB5673.namprd11.prod.outlook.com>
> Updated in v3 - Commit message:
> Update the QSPI flash layout to support UBIFS in mtd root partition.
> Flash layout is updated in order to store non-UBIFS related boot and fpga data in qspi_boot(mtd0)
> while keep the rootfs with UBIFS in the root partition(mtd1).
I got the impression that this change description is also improvable a bit.
How do you think about a wording variant like the following?
Non-UBIFS related boot and fpga data should be stored in qspi_boot (mtd0)
while keeping the rootfs with UBIFS in the root partition “mtd1”.
Thus update the QSPI flash layout to support UBIFS in the mtd root partition.
Will similar adjustments become helpful for subsequent update steps?
Regards,
Markus
prev parent reply other threads:[~2023-06-23 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230622123432.593548-1-kah.jing.lee@intel.com>
2023-06-22 13:05 ` [cocci] [PATCH v2 1/2] arm64: dts: agilex/stratix10: Updated QSPI Flash layout for UBIFS Markus Elfring
[not found] ` <PH0PR11MB56730E97D182D413C9B555E1CB23A@PH0PR11MB5673.namprd11.prod.outlook.com>
2023-06-23 11:03 ` Markus Elfring [this message]
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=c15e650e-6aee-d3e1-3fe1-7e5d34813a04@web.de \
--to=markus.elfring@web.de \
--cc=alif.zakuan.yuslaimi@intel.com \
--cc=catalin.marinas@arm.com \
--cc=cocci@inria.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=kah.jing.lee@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=will@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).