From: Khem Raj <raj.khem@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] webkitgtk: Fix build on 32bit platforms without 64bit atomics
Date: Wed, 29 Mar 2023 12:11:45 -0700 [thread overview]
Message-ID: <f0482727-b55f-3a79-7bf0-e3f61ec04c86@gmail.com> (raw)
In-Reply-To: <CANNYZj8PNKJLz+r9XTUbEan2c-MY3db7iiNzxeOpA0-ATtLUBw@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 753 bytes --]
On 3/29/23 12:04 PM, Alexander Kanavin wrote:
> On Wed, 29 Mar 2023 at 17:07, Khem Raj <raj.khem@gmail.com> wrote:
>>> 32-bit specificity is not in itself inappropriate for upstream
>>> submission, can you please either submit upstream or open a ticket and
>>> refer to it in the patch?
>>
>> did you read the message trail on the gerrit review I added to commit ?
>
> I did - upstream suggested a workaround that was submitted here (in an
> already closed merge request), but they didn't definitively say
> whether they would reject a ticket (or a patch) to solve the problem
> properly, so I think it's worth to at least open a ticket.
>
that is still under discussion. Hopefully they are amenable for such
accommodation
> Alex
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2613 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2023-03-29 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 21:43 [PATCH] webkitgtk: Fix build on 32bit platforms without 64bit atomics Khem Raj
2023-03-29 8:37 ` [OE-core] " Alexander Kanavin
2023-03-29 15:07 ` Khem Raj
2023-03-29 19:04 ` Alexander Kanavin
2023-03-29 19:11 ` Khem Raj [this message]
2023-03-30 10:13 ` Alexander Kanavin
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=f0482727-b55f-3a79-7bf0-e3f61ec04c86@gmail.com \
--to=raj.khem@gmail.com \
--cc=alex.kanavin@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