public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <uvv.mail@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v3] overlayfs: Fix the QA skip for ignored mounts
Date: Wed, 14 Jan 2026 14:34:05 +0100	[thread overview]
Message-ID: <DFOCNB99ON3M.1501I9LD79WEW@bootlin.com> (raw)
In-Reply-To: <20260113093218.348105-1-uvv.mail@gmail.com>

Hi,

You have sent multiple versions of some patches (v3 for 1/4, v2 for the rest,
I think): it's not straightforward for maintainers to follow which patch version
to apply.

I also see Paul has made some comment about the naming order of the patch
titles.

Can you take Paul's comments into account, and can you please re-send the series
with the proper versions of the patches? All patches should have the same
version.

Thanks!
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2026-01-14 13:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 14:16 [PATCH v2 1/4] overlayfs: Fix QA failure uvv.mail
2025-12-24 14:16 ` [PATCH v2 2/4] overlayfs: oe-selftest: Make the test more deterministic uvv.mail
2026-01-08 13:33   ` [OE-core] " Paul Barker
2026-01-09  8:49     ` Vyacheslav Yurkov
     [not found]     ` <188903DB96F81C7D.2783356@lists.openembedded.org>
2026-01-14  7:45       ` Vyacheslav Yurkov
2025-12-24 14:16 ` [PATCH v2 3/4] overlayfs: Remove helper unit uvv.mail
2025-12-24 14:16 ` [PATCH v2 4/4] oe-selftest: overlayfs: Add a demo case for /etc uvv.mail
2026-01-08 13:46   ` [OE-core] " Paul Barker
2026-01-09  8:52     ` Vyacheslav Yurkov
2026-01-08 13:21 ` [OE-core] [PATCH v2 1/4] overlayfs: Fix QA failure Paul Barker
2026-01-13  9:32   ` [PATCH v3] overlayfs: Fix the QA skip for ignored mounts uvv.mail
2026-01-14 13:34     ` Antonin Godard [this message]

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=DFOCNB99ON3M.1501I9LD79WEW@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=uvv.mail@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