[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALLGbRKs0hRLpRFz1mUJyKZan7Lf0eGAArJbBpXwFu2TQzcmWQ@mail.gmail.com>
Date: Sun, 27 Jun 2021 11:28:47 -0700
From: Steve deRosier <derosier@...il.com>
To: Pintu Agarwal <pintu.ping@...il.com>
Cc: Richard Weinberger <richard.weinberger@...il.com>,
open list <linux-kernel@...r.kernel.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
Richard Weinberger <richard@....at>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Phillip Lougher <phillip@...ashfs.org.uk>,
Sean Nyekjaer <sean@...nix.com>,
Kernelnewbies <kernelnewbies@...nelnewbies.org>
Subject: Re: Query: UBIFS: How to detect empty volumes
On Sun, Jun 27, 2021 at 6:52 AM Pintu Agarwal <pintu.ping@...il.com> wrote:
> But, it might be possible that some developer may miss/skip this
> firmware copying part, thus
This is your root problem.
If your build system requires any "magic incantations" such that it is
even possible that a developer can miss a step and result in this
situation, you *must* solve this problem. I don't know what you're
doing, but honestly, this shouldn't be much more than adding a line or
two into a Makefile or build.sh script. Fix this first.
I'm not saying it's a bad thing for your on-target flashing system to
sanity check the images, but that will never fix a broken process. Fix
the broken process.
- Steve
Powered by blists - more mailing lists