Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: SunilKumar.Dora@windriver.com, openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [kirkstone][PATCH] glibc: pthreads NPTL: lost wakeup fix
Date: Wed, 4 Jun 2025 17:16:55 +0200	[thread overview]
Message-ID: <4832019c-26dc-4f50-ad31-3145fda752a2@gmail.com> (raw)
In-Reply-To: <20250604144814.3103080-1-sunilkumar.dora@windriver.com>

Unfortunately I find this quite hard to review due to its size and the
number of commits included. Please, would that be possible to add a
separate patch for each relevant commit, instead of one mega-patch?


  reply	other threads:[~2025-06-04 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 14:48 [kirkstone][PATCH] glibc: pthreads NPTL: lost wakeup fix sunilkumar.dora
2025-06-04 15:16 ` Gyorgy Sarvari [this message]
2025-06-04 16:09   ` Dora, Sunil Kumar
2025-06-04 17:55     ` [OE-core] " Randy MacLeod

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=4832019c-26dc-4f50-ad31-3145fda752a2@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=SunilKumar.Dora@windriver.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