All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yang Xu" <yang.xu@mediatek.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] sstatesig: Fix pn and taskname derivation in find_siginfo
Date: Sun, 09 Jul 2023 07:34:34 -0700	[thread overview]
Message-ID: <6806.1688913274077356918@lists.openembedded.org> (raw)
In-Reply-To: <202307071236355ddab32a@mail.local>

[-- Attachment #1: Type: text/plain, Size: 331 bytes --]

Dear Alexandre,

Thank you for your reminder.

v1: correct handling for pn and taskname for native target in find_siginfo
v2: add handling for multilib target in find_siginfo
v3: add testcase for compare_sigfiles and find_siginfo work together.

Do I need submit a patch v4 to add these changlog information?

Thank you

[-- Attachment #2: Type: text/html, Size: 442 bytes --]

  reply	other threads:[~2023-07-09 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  6:52 [PATCH v3] sstatesig: Fix pn and taskname derivation in find_siginfo yang.xu
2023-07-07 12:36 ` [OE-core] " Alexandre Belloni
2023-07-09 14:34   ` Yang Xu [this message]
2023-07-10 11:43     ` Ross Burton
2023-07-09 14:48   ` Yang Xu (徐扬)
2023-07-10 21:04 ` Alexandre Belloni

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=6806.1688913274077356918@lists.openembedded.org \
    --to=yang.xu@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.