From: "florian.bezdeka@siemens.com" <florian.bezdeka@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "amikan@ilbers.de" <amikan@ilbers.de>,
"henning.schild@siemens.com" <henning.schild@siemens.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"florian.bezdeka@siemens.com" <florian.bezdeka@siemens.com>
Subject: [PATCH 0/2] Revert wic Y2038 series
Date: Mon, 15 Feb 2021 10:44:16 +0000 [thread overview]
Message-ID: <20210215104357.18632-1-florian.bezdeka@siemens.com> (raw)
From: Florian Bezdeka <florian.bezdeka@siemens.com>
I sent out an RFC series to fetch some comments / feedback regarding the
wic related changes to warn on Y2038 affected file system configurations.
As it turned out this series was already applied to `next`. This has to
be reverted until upstream (the OE project) accepts these changes. The
patch will be submitted soon. (I'm waiting for some kind of internal
approval to do so)
The second patch should be reverted for sure, but the fist one could
stay unreverted if maintainers like it.
@Anton: Please take care of patches / series tagged with "RFC" in the
future. Thanks!
Florian Bezdeka (2):
Revert "wic-img: Forward warnings from wic to bitbake"
Revert "wic: Warn if an ext filesystem affected by the Y2038 problem
is used"
meta/classes/wic-img.bbclass | 20 +++++--------------
scripts/lib/wic/partition.py | 38 ------------------------------------
2 files changed, 5 insertions(+), 53 deletions(-)
--
2.29.2
next reply other threads:[~2021-02-15 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHXA4eGCyAaaBIRYkefwrjJFwY5pw==>
2021-02-15 10:44 ` florian.bezdeka [this message]
2021-02-15 10:44 ` [PATCH 1/2] Revert "wic-img: Forward warnings from wic to bitbake" florian.bezdeka
2021-02-15 10:44 ` [PATCH 2/2] Revert "wic: Warn if an ext filesystem affected by the Y2038 problem is used" florian.bezdeka
2021-03-02 19:49 ` vijaikumar....@gmail.com
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=20210215104357.18632-1-florian.bezdeka@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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