From: "Mark Jonas" <mark.jonas@de.bosch.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Steve Sakoman <steve@sakoman.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"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>,
"quentin.schulz@streamunlimited.com"
<quentin.schulz@streamunlimited.com>
Subject: Re: Request to backport KERNEL_DTC_FLAGS to Dunfell
Date: Wed, 16 Jun 2021 15:28:12 +0000 [thread overview]
Message-ID: <8f04ab75284a42e084c02519d177bd18@de.bosch.com> (raw)
In-Reply-To: <CADkTA4NkMjTjTJbp_6HCapzasyzrWGwQkBWuen7GWgNi4ppZbw@mail.gmail.com>
Hi Bruce and Steve,
> Von: Bruce Ashfield <bruce.ashfield@gmail.com>
> On Fri, Jun 4, 2021 at 11:09 AM Steve Sakoman <steve@sakoman.com> wrote:
> >
> > On Fri, Jun 4, 2021 at 2:45 AM Jonas Mark (BT-FIR/ENG1-Grb)
> > <Mark.Jonas@de.bosch.com> wrote:
> > >
> > > 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"
[cut out web links messed up by Outlook]
> > > makes that possible in a nice way. Would it be reasonable to request
> backporting of this patch to Dunfell?
> >
> > This is sort of in the grey area between feature and bug fix. It does
> > seem relatively safe, so I would consider taking the patch if there
> > are no objections from the community.
> >
> > Added Bruce to the cc list to get his opinion.
>
> Good timing, I happened to notice this earlier and was thinking about it.
>
> While I also wouldn't call it a bug, I agree it is a small/standalone change that
> shouldn't break anything.
>
> A quick scan of the dunfell tested kernels shows unchanged Makefile handling of
> the option, so there's little risk there.
>
> I'd say that it would be fine for backport.
Can I help with the backport in any way?
My colleague Tingquan gave it a try and the patch from Hardknott applies cleanly on Dunfell.
The documentation patch for Poky proposed by Quentin does not apply though. But it is just that ref-variables.rst was renamed to variables.rst.
>
> Bruce
>
> >
> > > 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?
> >
> > No, there is no equivalent of bbappend for classes.
> >
> > Other solutions are possible, but taking this patch would be the
> > cleanest solution to your problem. Let's see what others think before
> > we go there :-)
> >
> > Steve
Cheers,
Mark
next prev parent reply other threads:[~2021-06-16 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 12:45 Request to backport KERNEL_DTC_FLAGS to Dunfell Mark Jonas
2021-06-04 15:09 ` 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 [this message]
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=8f04ab75284a42e084c02519d177bd18@de.bosch.com \
--to=mark.jonas@de.bosch.com \
--cc=Tingquan.Ruan@cn.bosch.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ovidiu.panait@windriver.com \
--cc=quentin.schulz@streamunlimited.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