From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ashishkumar.mishra@bmwtechworks.in>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] shared/fdset: add detailed debug logging to fdset_new_fill()
Date: Mon, 09 Mar 2026 08:26:06 +0100 [thread overview]
Message-ID: <DGY2MZH9OGCJ.8XW3AQX0RNI0@bootlin.com> (raw)
In-Reply-To: <317026.1773030655249324672@lists.openembedded.org>
On Mon Mar 9, 2026 at 5:30 AM CET, AshishKumar Mishra via lists.openembedded.org wrote:
> Hi Team,
>
> Any input on this patch
> I have backported this patch which i have merged in systemd upstream code base
> I could not see this patch in master-next branch of openembedded-core - OpenEmbedded Core layer ( https://git.openembedded.org/openembedded-core/log/?h=master-next )
> Hence wanted to check if there is any feedback from team
>
> Thanks .
> Ashish
Hi Ashish,
Yes, I had your patch aside for a few days, as a systemd upgrade to
259.1/259.3 was already sent and conflicting with your patch. This
upgrade is now merged.
Is your patch still needed with systemd 259.3? If that's the case, can
you please rebase on top of master?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-09 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 8:12 [PATCH] shared/fdset: add detailed debug logging to fdset_new_fill() Ashish Kumar Mishra
2026-03-09 4:30 ` AshishKumar Mishra
2026-03-09 7:26 ` Mathieu Dubois-Briand [this message]
2026-03-10 8:51 ` AshishKumar Mishra
2026-03-12 7:33 ` Ashish Mishra
2026-03-12 7:57 ` [OE-core] " Yoann Congal
-- strict thread matches above, loose matches on Subject: below --
2026-03-10 8:09 Ashish Kumar Mishra
2026-03-12 7:45 ` [OE-core] " Yoann Congal
2026-03-13 17:03 ` Peter Kjellerstedt
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=DGY2MZH9OGCJ.8XW3AQX0RNI0@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=ashishkumar.mishra@bmwtechworks.in \
--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