From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: "Jiang, Yi (T CED OES-DE)" <yi.jiang@siemens.com>,
"Kiszka, Jan (T CED)" <jan.kiszka@siemens.com>,
"xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: [PATCH 2/3] rpi4: Add rpi4 (Raspberry Pi 4) as target platform
Date: Thu, 23 May 2024 10:46:44 +0200 [thread overview]
Message-ID: <82b54361348112dc220d25db6c12f284898ddd2d.camel@siemens.com> (raw)
In-Reply-To: <92eb843ac00112e48b460f6b87e4c615dc8fb943.camel@siemens.com>
On Wed, 2024-05-22 at 12:35 +0000, Jiang, Yi (T CED OES-DE) wrote:
> > Confused.
> >
> > - My original patch did not touch the arm64 defconfig.
> > So I'm still listed as author ("From:" inside the body) but the
> > patch
> > content is different.
> >
>
> Yes, we do not need to keep rpi4.cfg any more, because the original
> content of rpi4.cfg has been merged to arm64_defconfig.
If that really works (especially for the older ipipe kernels for
tersting xenomai stable branches) the patch needs some reworking.
Florian
next prev parent reply other threads:[~2024-05-23 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 13:48 [PATCH 1/3] rpi-firmware: Add recipe for building version 20230405 Yi Jiang
2024-05-21 13:48 ` [PATCH 2/3] rpi4: Add rpi4 (Raspberry Pi 4) as target platform Yi Jiang
2024-05-21 14:52 ` Jan Kiszka
2024-05-21 15:57 ` Florian Bezdeka
2024-05-22 12:35 ` Jiang, Yi
2024-05-23 8:46 ` Florian Bezdeka [this message]
2024-05-23 14:16 ` Jan Kiszka
2024-05-23 14:19 ` Florian Bezdeka
2024-05-21 13:48 ` [PATCH 3/3] rpi4: add building options, remove old kernel and Xenomai versions in kas menu Yi Jiang
2024-05-21 14:54 ` Jan Kiszka
2024-05-22 12:37 ` Jiang, Yi
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=82b54361348112dc220d25db6c12f284898ddd2d.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
--cc=yi.jiang@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).