From: Vladislav Khmelevsky <och95@yandex.ru>
To: Alan Modra <amodra@gmail.com>
Cc: Dmitry Selyutin <ghostmansd@gmail.com>, binutils@sourceware.org
Subject: Re: [PATCH] Fix emit-relocs for aarch64 gold
Date: Thu, 16 Nov 2023 19:35:10 +0400 [thread overview]
Message-ID: <798116B7-6CA6-49B8-BD1F-7CCA7EBF8A91@yandex.ru> (raw)
In-Reply-To: <ZVXwV3+V0s0aNB2Y@squeak.grove.modra.org>
Alan, Dmitry thanks for your help. Appreciate that!
> 16 нояб. 2023 г., в 14:35, Alan Modra <amodra@gmail.com> написал(а):
>
> On Mon, Nov 13, 2023 at 11:15:09AM +0300, Dmitry Selyutin wrote:
>> On Wed, Nov 8, 2023 at 7:37 PM Vladislav Khmelevsky <och95@yandex.ru> wrote:
>>>
>>> It's been ~10 months I'm trying to submit the patch and no one replied on this even ones..
>>> Is there anything I can do to pay attention to this patch from the highly respected maintainers?
>>
>> Alan, could you, please, take a look at this patch, or kindly route
>> Vladislav to the right person?
>
> I've pushed the patch after fixing formatting. gold sources don't put
> a space before a function call opening parenthesis.
>
> --
> Alan Modra
> Australia Development Lab, IBM
next prev parent reply other threads:[~2023-11-16 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 16:26 Vladislav Khmelevsky
2023-11-08 16:36 ` Vladislav Khmelevsky
2023-11-13 8:15 ` Dmitry Selyutin
2023-11-16 10:35 ` Alan Modra
2023-11-16 15:35 ` Vladislav Khmelevsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-18 10:53 Vladislav Khmelevsky
2023-04-23 17:30 Vladislav Khmelevsky
2023-03-13 10:22 Vladislav Khmelevsky
2023-01-24 13:36 Vladislav Khmelevsky
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=798116B7-6CA6-49B8-BD1F-7CCA7EBF8A91@yandex.ru \
--to=och95@yandex.ru \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=ghostmansd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).