public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "rajmohan r" <semc.2042@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH] glibc-y2038-tests:add tests-special in run-built-tests yes
Date: Thu, 10 Apr 2025 03:10:55 -0700	[thread overview]
Message-ID: <13400.1744279855892849041@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj9wb4wkvhwmPnj=FmQAPu1G-oWDxeFGqNDZBLjHo6Fb5A@mail.gmail.com>

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

On Mon, Mar 31, 2025 at 11:26 AM, Alexander Kanavin wrote:

> 
> On Mon, 31 Mar 2025 at 13:13, rajmohan r via lists.openembedded.org
> <semc.2042=gmail.com@lists.openembedded.org> wrote:
> 
>> Since the change is in 'Make[file/rules]' and 'Rules' file,
>> so upstreamed for scarthgap branch.
>> Once the scarthgap patch is reviewed and no comment or
>> any comment is present, this scarthgap patch will help to
>> avoid extra-work for master branch. Hence upstreamed to
>> scarthgap branch.
> 
> That's not how the oe-core patch submission process works. Internally
> you can write and test patches in any order you like, but when sending
> them here for review, you must submit for master first.

I have send the patch to master branch and the link is https://lists.openembedded.org/g/openembedded-core/topic/patch_glibc_y2038_tests_add/112188476

> 
> Alex

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

      reply	other threads:[~2025-04-10 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 12:40 [scarthgap][PATCH] glibc-y2038-tests:add tests-special in run-built-tests yes rajmohan r
2025-03-28 13:18 ` [OE-core] " Alexander Kanavin
2025-03-31 11:13   ` rajmohan r
2025-03-31 11:26     ` [OE-core] " Alexander Kanavin
2025-04-10 10:10       ` rajmohan r [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=13400.1744279855892849041@lists.openembedded.org \
    --to=semc.2042@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