From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Quentin Schulz <quentin.schulz@cherry.de>,
mike.looijmans@topic.nl,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] meta: uboot-config: Fix broken menuconfig for "fitImage" kernel
Date: Fri, 24 May 2024 11:22:39 +0100 [thread overview]
Message-ID: <4a28c790acf8e06fd67761a6867dfe5fe412d8b3.camel@linuxfoundation.org> (raw)
In-Reply-To: <da23b251-8a2e-4bf1-8c96-812593f52d96@cherry.de>
On Thu, 2024-05-23 at 15:43 +0200, Quentin Schulz wrote:
> I was about to comment on the v2 that this should rather be a class :)
> Do we have some information on how/why this is the direction the project
> should move towards? What are the pitfalls we're trying to avoid, or
> benefits we want to gain? Or is this just some better/best practice we
> want to go for?
There was a post from me a while back complaining about repeatedly
splitting class files into smaller less manageable ones so that people
could access some variables without the task/function side effects.
I have a belief that more configuration files would help this kind of
problem and make classes more specific/focused and usable.
Cheers,
Richard
next prev parent reply other threads:[~2024-05-24 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.cc544a93-e646-4932-8496-82717a21cde8@emailsignatures365.codetwo.com>
2024-05-21 13:57 ` [PATCH] meta: uboot-config: Fix broken menuconfig for "fitImage" kernel Mike Looijmans
2024-05-21 14:51 ` [OE-core] " Richard Purdie
2024-05-22 5:28 ` mike.looijmans
2024-05-22 5:39 ` Richard Purdie
2024-05-22 6:43 ` mike.looijmans
2024-05-23 13:43 ` Quentin Schulz
2024-05-24 10:03 ` mike.looijmans
2024-05-24 10:22 ` Richard Purdie [this message]
2024-05-28 5:20 ` mike.looijmans
2024-05-28 10:01 ` Quentin Schulz
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=4a28c790acf8e06fd67761a6867dfe5fe412d8b3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@cherry.de \
/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