From: "Mark Jonas" <mark.jonas@de.bosch.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"steve@sakoman.com" <steve@sakoman.com>
Cc: "ovidiu.panait@windriver.com" <ovidiu.panait@windriver.com>,
"richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"toertel@gmail.com" <toertel@gmail.com>,
"RUAN Tingquan (BT-FIR/ENG1-Zhu)" <Tingquan.Ruan@cn.bosch.com>
Subject: Request to backport KERNEL_DTC_FLAGS to Dunfell
Date: Fri, 4 Jun 2021 12:45:22 +0000 [thread overview]
Message-ID: <d8dac798fed14554b0bfb5b7ea2daf12@de.bosch.com> (raw)
Hi,
We are using DT overlays and have the need to pass the -@ parameter in DTC_FLAGS to Linux' make. The patch
"kernel-devicetree: Introduce KERNEL_DTC_FLAGS to pass dtc flags"
https://git.openembedded.org/openembedded-core/commit/?h=hardknott&id=063b5de86624a42b0aa784db6dddc7552a6dee7f
makes that possible in a nice way. Would it be reasonable to request backporting of this patch to Dunfell?
We were also wondering what could be an alternative approach for getting this or a similar functionality. Patching a bbclass using a bbappend is not possible, is it?
Cheers,
Mark
Mark Jonas
Building Technologies, Panel Software Fire (BT-FIR/ENG1-Grb)
Bosch Sicherheitssysteme GmbH | Postfach 11 11 | 85626 Grasbrunn | GERMANY | www.boschsecurity.com
Tel. +49 89 6290-1105 | Telefax +49 89 6290-281105 | Mark.Jonas@de.bosch.com
Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart HRB 23118
Aufsichtsratsvorsitzender: Christian Fischer; Geschäftsführung: Thomas Quante, Andreas Bartz
next reply other threads:[~2021-06-04 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 12:45 Mark Jonas [this message]
2021-06-04 15:09 ` Request to backport KERNEL_DTC_FLAGS to Dunfell Steve Sakoman
2021-06-04 15:25 ` Bruce Ashfield
2021-06-07 8:49 ` [OE-core] " Quentin Schulz
2021-06-16 15:28 ` Mark Jonas
2021-06-16 15:53 ` Steve Sakoman
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=d8dac798fed14554b0bfb5b7ea2daf12@de.bosch.com \
--to=mark.jonas@de.bosch.com \
--cc=Tingquan.Ruan@cn.bosch.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ovidiu.panait@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=steve@sakoman.com \
--cc=toertel@gmail.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