Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <dixitparmar19@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] meta/meta-selftest: add selftest-hello-mod recipe
Date: Thu, 19 Jun 2025 13:40:25 +0200	[thread overview]
Message-ID: <DAQHCF8TSZCA.2ZCCQ2WA746D1@bootlin.com> (raw)
In-Reply-To: <22191.1750312600030991891@lists.openembedded.org>

On Thu Jun 19, 2025 at 7:56 AM CEST, Dixit Parmar via lists.openembedded.org wrote:
> On Thu, Jun 19, 2025 at 10:15 AM, Mathieu Dubois-Briand wrote:
>
>> 
>> On Mon Jun 9, 2025 at 3:41 PM CEST, Dixit Parmar via
>> lists.openembedded.org wrote:
>> 
>>> Kernel module specific oe test cases requires a test kernel
>>> module package to work with. Added selftest-hello-mod
>>> derived from meta-skeleton/recipes-kernel/hello-mod.
>>> 
>>> Signed-off-by: Dixit Parmar <dixitparmar19@gmail.com>
>>> ---
>> 
>> Thanks or your patch.
>> 
>> 
>>> +S = "${WORKDIR}/hello-mod"
>> 
>> This will trigger an error if some patches in master-next are merged,
>> you can rebase on master-next to see the error. The hello-mod recipe of
>> meta-skeleton was also updated accordingly.
>
> Do you mean I should take the latest reference from master-next for the meta-skeleton/hello-mod to meta-selftest?
>

All I can say for sure is we cannot take both the series from Alexander
and your patch as-is.

So as I believe the said series is likely to be merged, I would indeed
suggest to modify your patch accordingly, and this can be done by taking
the last version of meta-skeleton/hello-mod. But again, I'm not the one
deciding what gets merged, so I cannot be sure if and when it will be
merged.

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-06-19 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 13:41 [PATCH v2] meta/meta-selftest: add selftest-hello-mod recipe Dixit Parmar
2025-06-09 14:54 ` [OE-core] " Gyorgy Sarvari
2025-06-18 12:29   ` Dixit Parmar
2025-06-19  4:45 ` [OE-core] " Mathieu Dubois-Briand
2025-06-19  5:56   ` Dixit Parmar
2025-06-19 11:40     ` Mathieu Dubois-Briand [this message]
2025-06-19 11:56       ` Dixit Parmar
2025-06-21  7:32         ` Dixit Parmar

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=DAQHCF8TSZCA.2ZCCQ2WA746D1@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=dixitparmar19@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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