From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <semc.2042@gmail.com>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1])
	by smtp.lore.kernel.org (Postfix) with ESMTP id E4B5AC3601E
	for <webhook@archiver.kernel.org>; Thu, 10 Apr 2025 10:10:59 +0000 (UTC)
Subject: Re: [scarthgap][PATCH] glibc-y2038-tests:add tests-special in run-built-tests yes
To: openembedded-core@lists.openembedded.org
From: "rajmohan r" <semc.2042@gmail.com>
X-Originating-Location: AU (167.103.54.172)
X-Originating-Platform: Linux Chrome 134
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Thu, 10 Apr 2025 03:10:55 -0700
References: <CANNYZj9wb4wkvhwmPnj=FmQAPu1G-oWDxeFGqNDZBLjHo6Fb5A@mail.gmail.com>
In-Reply-To: <CANNYZj9wb4wkvhwmPnj=FmQAPu1G-oWDxeFGqNDZBLjHo6Fb5A@mail.gmail.com>
Message-ID: <13400.1744279855892849041@lists.openembedded.org>
Content-Type: multipart/alternative; boundary="xpwuQX3MpY3yNPwG7Hpa"
List-Id: <openembedded-core.lists.openembedded.org>
X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by
 aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for
 <openembedded-core@lists.openembedded.org>; Thu, 10 Apr 2025 10:10:59 -0000
X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/214637

--xpwuQX3MpY3yNPwG7Hpa
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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

>=20
> On Mon, 31 Mar 2025 at 13:13, rajmohan r via lists.openembedded.org
> <semc.2042=3Dgmail.com@lists.openembedded.org> wrote:
>=20
>> 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.
>=20
> 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.openem=
bedded.org/g/openembedded-core/topic/patch_glibc_y2038_tests_add/112188476

>=20
> Alex

--xpwuQX3MpY3yNPwG7Hpa
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<div>On Mon, Mar 31, 2025 at 11:26 AM, Alexander Kanavin wrote:</div>
<div>
<blockquote>On Mon, 31 Mar 2025 at 13:13, rajmohan r via lists.openembedded=
.org<br />&lt;semc.2042=3Dgmail.com@lists.openembedded.org&gt; wrote:<br />
<blockquote>Since the change is in 'Make[file/rules]' and 'Rules' file,<br =
/>so upstreamed for scarthgap branch.<br />Once the scarthgap patch is revi=
ewed and no comment or<br />any comment is present, this scarthgap patch wi=
ll help to<br />avoid extra-work for master branch. Hence upstreamed to<br =
/>scarthgap branch.</blockquote>
That's not how the oe-core patch submission process works. Internally<br />=
you can write and test patches in any order you like, but when sending<br /=
>them here for review, you must submit for master first.</blockquote>
</div>
<div>I have send the patch to master branch and the link is <a href=3D"http=
s://lists.openembedded.org/g/openembedded-core/topic/patch_glibc_y2038_test=
s_add/112188476" target=3D"_blank" rel=3D"noopener">https://lists.openembed=
ded.org/g/openembedded-core/topic/patch_glibc_y2038_tests_add/112188476</a>=
&nbsp;</div>
<div>
<blockquote>Alex</blockquote>
</div>

--xpwuQX3MpY3yNPwG7Hpa--