From: "Michael Adler" <michael.adler@siemens.com>
To: <nobuhiro1.iwamatsu@toshiba.co.jp>,
<felix.moessbauer@siemens.com>, <cip-dev@lists.cip-project.org>
Subject: Re: [PATCH 0/1] linux-cip: add kernel config snippet for container compatibility
Date: Tue, 28 Jan 2025 10:43:34 +0100 [thread overview]
Message-ID: <D7DLXLIXEJ2B.1FZ2QPQSTIG41@siemens.com> (raw)
In-Reply-To: <OS0PR01MB638822A2AA063548128D1A8192E32@OS0PR01MB6388.jpnprd01.prod.outlook.com>
Hi Nobuhiro,
thanks for your reply.
> Yes, please send us patches.
> There is no reason to distribute and manage CIP kernel configs.
I was hoping you could incorporate the options (which I sent in this patch) because I'm not really sure where to start:
- There seems to be a lot of duplication, even at the file level (e.g., `find . -name '*_defconfig' | xargs md5sum | awk '{ print $1; }' | sort | uniq -c`).
Do you manage everything manually, or do you have scripts to automate the process?
- Device-specific configs include non-device settings (e.g., cgroups, filesystems). In which file should the container settings go? cip_merged_defconfig or is that file auto-generated?
- There are kernel versions listed that were never LTS upstream (e.g., 6.11, 6.13). Are these versions officially supported by CIP?
Kind Regards,
Michael
--
Michael Adler
Siemens AG
Technology
Connectivity & Edge
Open Source Embedded Systems
FT RPD CED OES-DE
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim Hagemann
Snabe; Managing Board: Roland Busch, Chairman, President and Chief Executive
Officer; Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese;
Registered offices: Berlin and Munich, Germany; Commercial registries:
Berlin-Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
next prev parent reply other threads:[~2025-01-28 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 10:07 [PATCH 0/1] linux-cip: add kernel config snippet for container compatibility Michael Adler
2025-01-08 10:07 ` [PATCH 1/1] " Michael Adler
2025-01-09 8:11 ` [cip-dev] " Florian Bezdeka
2025-01-08 10:17 ` [PATCH 0/1] " MOESSBAUER, Felix
2025-01-09 7:58 ` Jan Kiszka
2025-01-24 6:07 ` nobuhiro1.iwamatsu
2025-01-28 9:43 ` Michael Adler [this message]
2025-01-30 21:57 ` nobuhiro1.iwamatsu
2025-02-03 16:35 ` Michael Adler
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=D7DLXLIXEJ2B.1FZ2QPQSTIG41@siemens.com \
--to=michael.adler@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=felix.moessbauer@siemens.com \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/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