From: Steve deRosier <derosier@gmail.com>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
Richard Weinberger <richard@nod.at>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Phillip Lougher <phillip@squashfs.org.uk>,
Sean Nyekjaer <sean@geanix.com>,
Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Query: UBIFS: How to detect empty volumes
Date: Sun, 27 Jun 2021 11:28:47 -0700 [thread overview]
Message-ID: <CALLGbRKs0hRLpRFz1mUJyKZan7Lf0eGAArJbBpXwFu2TQzcmWQ@mail.gmail.com> (raw)
In-Reply-To: <CAOuPNLj4ktYYieOqxd1EGUWt0DZamwQik_jg6cj2ZyqRaL9Amw@mail.gmail.com>
On Sun, Jun 27, 2021 at 6:52 AM Pintu Agarwal <pintu.ping@gmail.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
WARNING: multiple messages have this Message-ID (diff)
From: Steve deRosier <derosier@gmail.com>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
Richard Weinberger <richard@nod.at>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Phillip Lougher <phillip@squashfs.org.uk>,
Sean Nyekjaer <sean@geanix.com>,
Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Query: UBIFS: How to detect empty volumes
Date: Sun, 27 Jun 2021 11:28:47 -0700 [thread overview]
Message-ID: <CALLGbRKs0hRLpRFz1mUJyKZan7Lf0eGAArJbBpXwFu2TQzcmWQ@mail.gmail.com> (raw)
In-Reply-To: <CAOuPNLj4ktYYieOqxd1EGUWt0DZamwQik_jg6cj2ZyqRaL9Amw@mail.gmail.com>
On Sun, Jun 27, 2021 at 6:52 AM Pintu Agarwal <pintu.ping@gmail.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
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Steve deRosier <derosier@gmail.com>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: Kernelnewbies <kernelnewbies@kernelnewbies.org>,
Richard Weinberger <richard.weinberger@gmail.com>,
Richard Weinberger <richard@nod.at>,
open list <linux-kernel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
Sean Nyekjaer <sean@geanix.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Phillip Lougher <phillip@squashfs.org.uk>
Subject: Re: Query: UBIFS: How to detect empty volumes
Date: Sun, 27 Jun 2021 11:28:47 -0700 [thread overview]
Message-ID: <CALLGbRKs0hRLpRFz1mUJyKZan7Lf0eGAArJbBpXwFu2TQzcmWQ@mail.gmail.com> (raw)
In-Reply-To: <CAOuPNLj4ktYYieOqxd1EGUWt0DZamwQik_jg6cj2ZyqRaL9Amw@mail.gmail.com>
On Sun, Jun 27, 2021 at 6:52 AM Pintu Agarwal <pintu.ping@gmail.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
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-06-27 18:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 16:00 Query: UBIFS: How to detect empty volumes Pintu Agarwal
2021-06-24 16:09 ` Pintu Agarwal
2021-06-24 16:09 ` Pintu Agarwal
2021-06-24 16:09 ` Pintu Agarwal
2021-06-27 8:42 ` Richard Weinberger
2021-06-27 8:42 ` Richard Weinberger
2021-06-27 8:42 ` Richard Weinberger
2021-06-27 13:49 ` Pintu Agarwal
2021-06-27 13:49 ` Pintu Agarwal
2021-06-27 13:49 ` Pintu Agarwal
2021-06-27 18:28 ` Steve deRosier [this message]
2021-06-27 18:28 ` Steve deRosier
2021-06-27 18:28 ` Steve deRosier
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=CALLGbRKs0hRLpRFz1mUJyKZan7Lf0eGAArJbBpXwFu2TQzcmWQ@mail.gmail.com \
--to=derosier@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=phillip@squashfs.org.uk \
--cc=pintu.ping@gmail.com \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=sean@geanix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.